中介流使用的初始线程请求响应，并等待该服务的响应。
The original thread used by the mediation flow requests the response and waits for the response from the service.
客户端接收响应后，或者已提供响应，客户端继续在初始线程上处理(参见图2)。
After the response is received by the client, or if the response is already available, the client continues processing on the original thread (see Figure 2).
中介流使用的初始线程继续执行，但是此线程不能使用从被调用的服务返回的任何响应。
The original thread used by the mediation flow continues, but any response returned from the invoked service isn't available to this thread.
如果初始化的代价高昂，或者从多个线程中同时调用该代码，则这一重复创建的影响仍然可能成为问题。
If the initialization is expensive, or the code is called simultaneously from multiple threads, the impact of this repeated creation may still be an issue.
所有线程都有一个初始存储区，将在该线程的生命周期中使用。
All threads have an initial memory area that's used for the thread's lifetime.
如果提供初始数据之后仍可能存在交互，那么将连接保持为打开状态，因此线程就不能释放出来，服务器也就不能为很多用户服务。
If interaction was possible after the initial data was served, and the connection was kept open, then the thread could not be released and the server would not be able to serve many users.
不过，在中介流初始实例的执行线程上，将调用在服务调用原语的输入端上连接的任何其他中介原语。
However, on the thread of execution of the original instance of the mediation flow, any further mediation primitives wired on the input side of the service invoke primitive are invoked.
清单2中的线程2用于在整个时间段内拍摄多个快照，在初始复位监控器命令之后没有发出复位监控器命令。
Thread 2 in Listing 2 is for taking multiple snapshots over the period without issuing the reset monitor command after the initial reset monitor command.
现在只剩下两个次要的任务 ——初始化互斥锁和启动线程运行可上传的文件的列表。
This just leaves us with a couple of minor bookkeeping tasks -- initializing the mutex and starting a thread to run through the list of uploadable files.
在大内存模型中，本机堆从分段3开始；分段2仅用于原始(初始)线程栈。
In the large memory model, the native heap starts at segment 3; segment 2 is only used for the primordial (initial) thread stack.
线程1通过运行Singleton对象的构造函数并将引用返回给它，来完成对该对象的初始化。
Thread 1 completes the initialization of the Singleton object by running its constructor and returns a reference to it.
Stacksize也是一个极其重要的配置参数，它指示了数据库服务器为每个活动线程指派的初始堆栈的大小。
Stacksize is also a very important configuration parameter that indicates the initial stack size the database server assigns to each active thread.
RIFE初始的实现，基于性能的考虑，只设计使用一条线程来访问Map。
The initial RIFE implementation was designed to only access the map using a thread for performance reasons.
例如，如果您预期200个Web邮件用户，那么合适的初始http线程的数量为20。
For example, if you anticipate 200 Web mail users, a suitable initial setting for the HTTP threads is 20.
这两者都体现了延迟初始化的特性(因此又被称为futures)。前者是一个类，而后者则是一个轻量的，但并非“绝对”线程安全的结构。
Both support the idea of deferred initialization, also known as futures, the former is a class and the later a lightweight and slightly less safe structure.
这个参数表示在DB2START时在db 2fmp池中创建的非线程化空闲db2f mp进程的初始数量。
This parameter indicates the initial number of non-threaded, idle db2fmp processes that are created in the db2fmp pool at DB2START time.
中断状态初始时为 false；当另一个线程通过调用 Thread.interrupt() 中断一个线程时，会出现以下两种情况之一。
The interrupted status is initially false; when a thread is interrupted by some other thread through a call to Thread.interrupt(), one of two things happens.
这些指令大多数是为了检查i的初始化，以及使用锁执行线程安全的初始化。
Most of these instructions are in place to check for the initialization of I, and to perform a thread-safe initialization using a lock.
中断的其他初始化工作都需要在这个线程中进行。
All other initializations for the interrupts should be carried out in this thread.
类似地，在初始化期间可以创建一个解析器池(每个线程创建一个)。
Similarly, you can create a pool of parsers-one per thread-at initialization time.
本文还讨论了如何在应用服务器上配置内存、线程池和JDBC连接池的初始值。
The article also discusses how to initially configure the memory, thread pool, and JDBC connection pool on the application server.
首先，它初始化这些系统类不需要线程支持来执行这些静态的初始化。
First, it initializes those system classes that don't require thread support by executing their static initializers.
还有一种可能是在启动时派生一个单独的低优先级的线程，当系统空闲时再去完成初始化，不过这种方法需要特别注意处理好同步。
Another possibility is to fork a separate low-priority thread during startup to perform initialization when the system is idle, although this choice requires more care to handle synchronization.
您可以通过从一个高优先级rt线程执行应用程序初始化来避免这个问题。
You can avoid this problem by performing application initialization from a high-priority RT thread.
这样我们将可以传递实现每一个子线程初始化的场所对象。
Then we can pass along the locale object with each child thread initiation.
一旦线程被初始化，它们2个就作为一对存在。
Once the thread is properly initialized, the 2 will always exist as a pair.
完成初始化之后，HTTP线程必须得到正确处理。
The HTTP threads, once initialized, must be properly disposed.
然后这种说法并不完全正确；这时仍然有一个线程在运行，这个线程是进程初始运行时建立的线程。
This isn't quite true; there's one thread still running, the one the process started with.
然后，一个线程进入synchronized块来初始化instance，而另一个线程则被阻断。
Then, one thread enters the synchronized block to initialize instance, while the other is blocked.
然后，一个线程进入synchronized块来初始化instance，而另一个线程则被阻断。
Then, one thread enters the synchronized block to initialize instance, while the other is blocked.
应用推荐