[ViewVC] Diff of: cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.247 by root, Wed Jul 8 02:46:05 2009 UTC vs.
Revision 1.248 by root, Wed Jul 8 04:14:34 2009 UTC

 The callback is guaranteed to be invoked only I<after> its timeout has
 passed (not I<at>, so on systems with very low-resolution clocks this
 might introduce a small delay). If multiple timers become ready during the
 same loop iteration then the ones with earlier time-out values are invoked
-before ones with later time-out values (but this is no longer true when a
+before ones of the same priority with later time-out values (but this is
-callback calls C<ev_loop> recursively).
+no longer true when a callback calls C<ev_loop> recursively).
 =head3 Be smart about timeouts
 Many real-world problems involve some kind of timeout, usually for error
 recovery. A typical example is an HTTP request - if the other side hangs,
 but forking and registering a watcher a few event loop iterations later or
 in the next callback invocation is not.
 Only the default event loop is capable of handling signals, and therefore
 you can only register child watchers in the default event loop.
+Due to some design glitches inside libev, child watchers will always be
+handled at maximum priority (their priority is set to EV_MAXPRI by libev)
 =head3 Process Interaction
 Libev grabs C<SIGCHLD> as soon as the default event loop is
 initialised. This is necessary to guarantee proper behaviour even if

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines