Lines Matching refs:events
12 In event-driven programming, an application expresses interest in certain events
13 and respond to them when they occur. The responsibility of gathering events
14 from the operating system or monitoring other sources of events is handled by
20 while there are still events to process:
25 Some examples of events are:
53 queue. The application can inspect the events at its convenience (perhaps doing
59 events can be treated as just another libuv event. The non-blocking ensures
60 that other events can continue to be handled as fast as they come in [#]_.
93 This program quits immediately because it has no events to process. A libuv
94 event loop has to be told to watch out for events using the various API
139 libuv works by the user expressing interest in particular events. This is
