Sencha触摸jQuery Mobile(Sencha Touch over jquery Mobile)

 您可以将所需的任何数据传递给Thread.Start()方法。 这基本上是在线程之间共享内容的首选方式。 但是，在基本级别，如果多个线程要访问其他线程，那么您需要建立某种锁定机制以确保您没有争用问题。 
 
 假设您在线程之间共享一个全局级别的类实例： 
 
 （这是C＃，但你明白了） 
 
class GlobalData {

    public string SomeProperty {get; set; }
    public int SomeOtherProperty {get; set; }

}
 
 多个线程同时访问这些属性中的任何一个（或者期望值在调用之间保持一致）的情况将会很麻烦。 所以最简单的方法是创建一个线程负责的锁定机制： 
 
class GlobalData {

    public object Sentry = new object();

    public string SomeProperty {get; set; }
    public int SomeOtherProperty {get; set; }
}
 
 在运行线程的代码中，你会做这样的事情（假设g_Data是类的实例）： 
 
void SomeMethodRunningOnAThread() {
    lock (g_Data.Sentry) {
        // do stuff    
    }
}
 
 （在VB.NET中相当于lock是SyncLock ） 
 
 这是确保您不会遇到争用问题的最简单方法。 每个线程负责确保在访问对象之前尝试锁定对象。 
 
 除此之外，当然还有一些方法可以对此进行细化，例如在包含全局数据的类中实现锁定逻辑。 它不会变得那么复杂，所以如果你想要实现更复杂的东西，你最后还是必须阅读。 

You can pass any data you want to the Thread.Start() method. That's basically the preferred way of sharing stuff between threads. However, at a basic level, if more than one of the threads is going to access something that the others will as well, you need to establish some kind of locking mechanism to ensure you don't have contention issues.
 
Let's say you have a class instance at the global level that is shared among your threads:
 
(this is C# but you get the idea) 
 
class GlobalData {

    public string SomeProperty {get; set; }
    public int SomeOtherProperty {get; set; }

}
 
A scenario where more than one thread accesses any of these properties at the same time (or expect the value to be consistent across calls) would be trouble. So the easiest way is to create a locking mechanism where the thread is responsible:
 
class GlobalData {

    public object Sentry = new object();

    public string SomeProperty {get; set; }
    public int SomeOtherProperty {get; set; }
}
 
In the code that runs the threads, you would do something like this (assuming g_Data is the instance of the class):
 
void SomeMethodRunningOnAThread() {
    lock (g_Data.Sentry) {
        // do stuff    
    }
}
 
(in VB.NET the equivalent to lock is SyncLock)
 
This is the simplest way to ensure you don't get into contention issues. Each thread is responsible for ensuring that they are attempting a lock on the object before accessing its contents.
 
Beyond that, there are of course ways to finesse this, such as implementing the lock logic within the class that contains the global data. It doesn't get less complicated, so if you want to implement something more complex in the end you'll have to read up anyway.