Lines Matching refs:event
4 libuv enforces an **asynchronous**, **event-driven** style of programming. Its
5 core job is to provide an event loop and callback based notifications of I/O
12 In event-driven programming, an application expresses interest in certain events
15 libuv, and the user can register callbacks to be invoked when an event occurs.
16 The event-loop usually keeps running *forever*. In pseudocode:
21 e = get the next event
31 This event loop is encapsulated by ``uv_run()`` -- the end-all function when using
49 non-blocking** style. Most modern operating systems provide event notification
52 operating system to watch the socket and put an event notification in the
58 This fits in well with libuv's event-loop approach, since the operating system
59 events can be treated as just another libuv event. The non-blocking ensures
73 libuv's event loop is explained in more detail in the `documentation
94 event loop has to be told to watch out for events using the various API
203 Callbacks are functions which are called by libuv whenever an event the watcher
213 every turn of the event loop. A use case for idle handles is discussed in
217 event watchers are active.
