Date: Mon, 12 Nov 2007 08:11:01 +0000 Subject: [PATCH] *** empty log message *** --- ev.html | 16 ++++++++-------- ev.pod | 4 +++- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/ev.html b/ev.html index 3976c09..95a6bf7 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -28,7 +28,7 @@

struct ev_io - is my file descriptor readable or writable
struct ev_timer - relative and optionally recurring timeouts
ev_periodic
ev_periodic - to cron or not to cron it
ev_signal - signal me when a signal gets signalled
ev_child - wait for pid status changes
ev_idle - when you've got nothing better to do

Libev is an event loop: you register interest in certain events (such as a file descriptor being readable or a timeout occuring), and it will manage -these event sources and provide your program events.

+these event sources and provide your program with events.

To do this, it must take more or less complete control over your process (or thread) by executing the event loop handler, and will then communicate events via a callback mechanism.

@@ -318,8 +318,8 @@ corresponding stop function (ev_<type>_stop (loop, watcher *)

As long as your watcher is active (has been started but not stopped) you must not touch the values stored in it. Most specifically you must never reinitialise it or call its set method.

You cna check wether an event is active by calling the ev_is_active -(watcher *) macro. To see wether an event is outstanding (but the +

You cna check whether an event is active by calling the ev_is_active +(watcher *) macro. To see whether an event is outstanding (but the callback for it has not been called yet) you cna use the ev_is_pending (watcher *) macro.

Each and every callback receives the event loop pointer as first, the @@ -424,7 +424,7 @@ information given in the last section.

struct ev_io - is my file descriptor readable or writable

I/O watchers check wether a file descriptor is readable or writable +

I/O watchers check whether a file descriptor is readable or writable in each iteration of the event loop (This behaviour is called level-triggering because you keep receiving events as long as the condition persists. Remember you cna stop the watcher if you don't want to @@ -482,8 +482,8 @@ the timer, and again will automatically restart it if need be.

ev_periodic

ev_periodic - to cron or not to cron it

Periodic watchers are also timers of a kind, but they are very versatile (and unfortunately a bit complex).

Unlike ev_timer's, they are not based on real time (or relative time) diff --git a/ev.pod b/ev.pod index 3a6063f..2717062 100644 --- a/ev.pod +++ b/ev.pod @@ -27,7 +27,9 @@ Libev supports select, poll, the linux-specific epoll and the bsd-specific kqueue mechanisms for file descriptor events, relative timers, absolute timers with customised rescheduling, signal events, process status change events (related to SIGCHLD), and event watchers dealing with the event -loop mechanism itself (idle, prepare and check watchers). +loop mechanism itself (idle, prepare and check watchers). It also is quite +fast (see a L comparing it +to libevent). =head1 CONVENTIONS -- 2.43.0