Lines Matching refs:a
22 if there is a callback associated with e:
35 rather than a lot of number-crunching. The problem with using conventional
37 **blocking**. The actual write to a hard disk or reading from a network, takes
38 a disproportionately long time compared to the speed of the processor. The
40 nothing. For programs which require high performance this is a major roadblock
44 started in a separate thread (or in a thread pool). When the blocking function
50 subsystems. For example, a normal ``read`` call on a socket would block until
67 polling to perform tasks in a non-blocking manner.
69 Bert Belder, one of the libuv core developers has a small video explaining the
71 either libuv or libev, it is a quick, useful watch.
86 nothing, except start a loop which will exit immediately.
109 ``uv_default_loop()``. You should use this loop if you only want a single
127 …nchronous functions which may fail return a negative number on error. Async functions that may fai…
132 to get a ``const char *`` describing the error or the error name respectively.
134 I/O read callbacks (such as for files and sockets) are passed a parameter ``nread``. If ``nread`` i…
140 usually done by creating a **handle** to an I/O device, timer or process.
191 only one callback) and usually indicates one I/O operation on a handle.
194 a ``uv_udp_t``, while individual writes to the socket use a ``uv_udp_send_t``
197 Handles are setup by a corresponding::
206 the data read from a file, a timer callback will be triggered on timeout and so
215 and see how ``uv_run()`` will now block because a watcher is present. The idle
229 handles and requests have a ``void* data`` member which you can set to the
230 context and cast back in the callback. This is a common pattern used throughout
231 the C library ecosystem. In addition ``uv_loop_t`` also has a similar data
