Lines Matching refs:in
5 way** to do *web-scale programming*? Well... no. Threads are still the medium in
21 required, signal errors directly via return values, and, as shown in the
29 running in one thread (the main thread)**. No other thread interacts
54 custom parameters to the thread. The function ``hare`` will now run in a separate
72 catalogue any surprises in the libuv APIs here. For the rest you can look at
111 unlocks ``a_mutex`` but will lead to your program crashing if in debug mode, or
112 return an error in the second call to ``uv_mutex_lock()``.
124 holding it. Read-write locks are frequently used in databases. Here is a toy
138 We also use barriers in the above example so that the main thread can wait for
192 a task in a separate thread, and have a callback that is triggered when the
196 make sure that no function which runs periodically in the loop thread blocks
204 own system of running the task in a separate thread. libuv just provides
208 calculate fibonacci numbers, sleeping a bit along the way, but run it in
219 run in a separate thread. The ``uv_work_t`` structure is the clue. You can pass
233 The thread function will be launched in a separate thread, passed the
235 will be called on the thread the event loop is running in. It will be passed
296 they are running. For example you might be running some long duration task in
316 may be invoked immediately after ``uv_async_send`` is called in another
358 a mutex or rwlock to ensure accesses are performed in the right order.
366 libraries that require thread affinity for their functionality. For example in
368 that the v8 instance was started in. Interacting with v8 data structures from
387 3. The actual work being done in a separate thread wants to invoke the progress
391 4. The async callback, invoked in the main loop thread, which is the v8 thread,
