Lines Matching refs:in
12 In event-driven programming, an application expresses interest in certain events
44 started in a separate thread (or in a thread pool). When the blocking function
45 gets invoked in the thread, the operating system can schedule another thread to run,
52 operating system to watch the socket and put an event notification in the
56 point, then used the data at another point (in time and space). It is
58 This fits in well with libuv's event-loop approach, since the operating system
60 that other events can continue to be handled as fast as they come in [#]_.
64 How the I/O is run in the background is not of our concern, but due to the
67 polling to perform tasks in a non-blocking manner.
73 libuv's event loop is explained in more detail in the `documentation
98 initializing it with ``uv_loop_init(uv_loop_t *)``. This allows you to plug in
139 libuv works by the user expressing interest in particular events. This is
204 is interested in has taken place. Application specific logic will usually be
205 implemented in the callback. For example, an IO watcher's callback will receive
213 every turn of the event loop. A use case for idle handles is discussed in
230 context and cast back in the callback. This is a common pattern used throughout
