Lines Matching refs:callback
5 core job is to provide an event loop and callback based notifications of I/O
22 if there is a callback associated with e:
23 call the callback
191 only one callback) and usually indicates one I/O operation on a handle.
192 Requests are used to preserve context between the initiation and the callback
195 structure that is passed to the callback after the write is done.
205 implemented in the callback. For example, an IO watcher's callback will receive
206 the data read from a file, a timer callback will be triggered on timeout and so
212 Here is an example of using an idle handle. The callback is called once on
227 In callback based programming style you'll often want to pass some 'context' --
228 application specific information -- between the call site and the callback. All
230 context and cast back in the callback. This is a common pattern used throughout
