A debugger hijacking of a user thread.
调试器截获用户线程。
Marks this thread as either a daemon thread or a user thread.
每一个线程都被标记为“守护线程”或“用户线程”。
That value is returned from the ioctl call and the user thread must react to that.
这个值是从ioctl调用中返回的，用户线程必须对此进行响应。
A user thread is a database server thread that services requests from client applications.
用户线程是服务来自客户机应用程序的请求的数据库服务器线程。
After this foreground GC is finished, the background GC thread and the user threads can resume their work.
在前台垃圾收集完成之后，后台垃圾时线程和应用程序的线程就继续它们的工作。
This enables a 1:1 threading model without limitations on the number of threads being created (since a new kernel thread is created for every user thread).
这样就可以实现一个不受创建的线程数限制的1:1线程模型（因为每一个新的内核线程都是为一个用户线程而创建）。
A general solution for the problem above is to have each user thread hold a locale variable by passing the variable to the user thread during its construction.
对于以上问题通用的解决方法，是通过在构造变量期间将其传递给用户线程，来让每一个用户都有一个场所变量。
When the variable in ready inside of that thread, you can use the sample code listed in Listing 10 to get the globalization working for codes running in the user thread.
当变量在线程中准备好时，您可以使用列表10中所示的范例代码，来在用户线程中运行代码以实现全球化。
This usually means copying the arguments over from the spe local store, running the respective library function in the user thread, and continuing by calling the ioctl again.
这通常意味着从SPE的本地存储中拷贝参数，在用户线程中运行各自的库函数，并通过再次调用ioctl继续执行。
As the code in user thread constructor still runs in the caller thread's context, we have a chance to inherit a locale object from the servlet thread when the user thread is being constructed.
因为用户线程构造器中的代码仍然在访问线程的环境下运行，所以在构造用户线程时，我们还有机会从服务线程继承场所对象。
While a thread is running, either uploading or downloading, you can query it to check on its status to provide the user with feedback (e.g. a progress bar).
当一个线程在运行的时候，不管是上传还是下载，你可以查询进程状态并且给用户一个反馈（例如一个进度条）。
Each thread simulates a user that connects to the database and submits a stream of transactions without think times.
每个线程模拟一个用户，该用户连接到数据库并提交一个事务流，而不考虑次数。
A thread is created to handle each new user connection.
一个线程被创建来处理每个新用户连接。
The callback handler class has two thread local variables that can store the user ID and password from the client instance.
这个回调处理器类拥有两个线程本地变量，用于存储来自客户端实例的用户ID和密码。
While a thread is running, either uploading or downloading, you can query it to check on its status to provide the user with feedback (eg. a progress bar).
当一个线程在运行的时候，不管是上传还是下载，你可以查询进程状态并且给用户一个反馈(例如一个进度条)。
This caused each NRPC user to spawn off a server thread.
这就导致每个NRPC用户都会派生一个服务器线程。
This is because remote invocations in JSR 172 are blocking calls, and if invoked in the main event thread, the user interface will freeze until the remote invocation completes.
由于JSR 172中的远程调用是按模块进行的，而且如果在主事件线程中调用，用户界面会冻结，直到远程调用结束。
The single CSLD task thread services all jobs in a sequential way and connects to one user mailbox after the other to extract the mails.
一个CSLD任务线程按顺序为所有任务服务，并且逐个地连接到各个用户邮箱，以便提取邮件。
This approach is a little more limited, because it does not give you stateless performance — you are in fact using a separate thread per user.
这种方式有一点儿受限制，因为它不提供无状态性能——实际上是为每个用户使用一个单独的线程。
Even worse, if the UI thread is blocked for more than a few seconds (about 5 seconds currently) the user is presented with the infamous "application not responding" (ANR) dialog.
更坏的是，如果应用程序ui线程被阻塞超过几秒钟(现在大概是5秒)，用户就会看到一个让人不高兴的“应用程序没有响应”(ANR)对话框。
The only problem with this function is that when it periodically executes, it executes on the main thread and thus blocks any interactions from the user during that time.
此函数的惟一缺陷是：它在主线程上执行，因此，在此期间，它会阻塞与用户的任何交互。
Specifically, if everything is happening in a single thread, performing long operations such as network access or database queries on the UI thread will block the whole user interface.
特别是，如果把所有的事件都放在主线程中来处理，需要长时间来处理的事件比如网络访问或者数据库查询，会阻塞整个UI。
When a pluglet is executed, it runs on the Rational Software Architect (User Interface) UI thread.
当运行pluglet 时，它在RationalSoftware Architect（用户界面）UI 线程上运行。
In each case, the server provides the data that the user requests and can then close the connection, allowing that thread to be freed up to serve other requests.
在以上任何一种Web应用程序中，服务器提供用户请求的数据，然后关闭连接，并释放那个线程，使之可以为其他请求服务。
This in turn results in one thread per user on Tomcat, while the NIO server handles the same load with a constant number of threads.
然后它导致了在Tomcat上为每个用户分配一个线程，而NIO 服务器用固定数量的线程来处理相同的负载。
The Linux kernel provides a lightweight process framework for creating threads; the actual thread implementation is in the user space.
Linux内核提供了一个轻量级进程框架来创建线程；实际的线程在用户空间中实现。
If synchronous and asynchronous requests are allowed to be submitted concurrently, this situation can mean supporting at least one more thread consumption (for the Ajax request) per user request.
如果允许并发地提交同步和异步请求，就意味着每个用户请求至少要支持多出一个的线程消耗(用于Ajax请求)。
You can access specific fields from the process, thread, user and MST structures.
可以访问进程、线程、用户和mst结构中的特定字段。
Keep in mind that Tomcat must allocate one thread per user, while the NIO server was configured with only four worker threads.
记住，Tomcat必须为每个用户分配一个线程，而NIO服务器只配置有4个工作线程。
The PresentationReconciler class updates the text's appearance with every keystroke, and the Reconciler class runs in a daemon thread, parsing the document without holding up the user interface (UI).
presentationreconciler类根据每次击键更新文本的外观，而Reconciler类运行一个守护线程，不必将用户界面(UI)挂起就能解析该文档。
应用推荐