*** empty log message ***

[software/libev.git] / ev.pod

diff --git a/ev.pod b/ev.pod
index 30439ef725ec9a5e72ca24da816a6c70b5196979..d1c5d63f8b79f42edf65ea8c37034d760e19fdf3 100644 (file)
--- a/ev.pod
+++ b/ev.pod
@@ -470,6 +470,7 @@ Example: for some weird reason, unregister the above signal handler again.
 
 =back
 
 
 =back
 

+

 =head1 ANATOMY OF A WATCHER
 
 A watcher is a structure that you create and register to record your
 =head1 ANATOMY OF A WATCHER
 
 A watcher is a structure that you create and register to record your


@@ -578,7 +579,7 @@ programs, though, so beware.
 
 =back
 
 
 =back
 

-=head2 SUMMARY OF GENERIC WATCHER FUNCTIONS
+=head2 GENERIC WATCHER FUNCTIONS

 
 In the following description, C<TYPE> stands for the watcher type,
 e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.
 
 In the following description, C<TYPE> stands for the watcher type,
 e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.


@@ -597,7 +598,7 @@ which rolls both calls into one.
 You can reinitialise a watcher at any time as long as it has been stopped
 (or never started) and there are no pending events outstanding.
 
 You can reinitialise a watcher at any time as long as it has been stopped
 (or never started) and there are no pending events outstanding.
 

-The callbakc is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,
+The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,

 int revents)>.
 
 =item C<ev_TYPE_set> (ev_TYPE *, [args])
 int revents)>.
 
 =item C<ev_TYPE_set> (ev_TYPE *, [args])


@@ -693,13 +694,15 @@ This section describes each watcher in detail, but will not repeat
 information given in the last section.
 
 
 information given in the last section.
 
 

-=head2 C<ev_io> - is this file descriptor readable or writable
+=head2 C<ev_io> - is this file descriptor readable or writable?

 
 I/O watchers check whether 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 can stop the watcher if you don't want to
-act on the event and neither want to receive future events).
+in each iteration of the event loop, or, more precisely, when reading
+would not block the process and writing would at least be able to write
+some data. This behaviour is called level-triggering because you keep
+receiving events as long as the condition persists. Remember you can stop
+the watcher if you don't want to act on the event and neither want to
+receive future events.

 
 In general you can register as many read and/or write event watchers per
 fd as you want (as long as you don't confuse yourself). Setting all file
 
 In general you can register as many read and/or write event watchers per
 fd as you want (as long as you don't confuse yourself). Setting all file


@@ -709,33 +712,37 @@ required if you know what you are doing).
 You have to be careful with dup'ed file descriptors, though. Some backends
 (the linux epoll backend is a notable example) cannot handle dup'ed file
 descriptors correctly if you register interest in two or more fds pointing
 You have to be careful with dup'ed file descriptors, though. Some backends
 (the linux epoll backend is a notable example) cannot handle dup'ed file
 descriptors correctly if you register interest in two or more fds pointing

-to the same underlying file/socket etc. description (that is, they share
+to the same underlying file/socket/etc. description (that is, they share

 the same underlying "file open").
 
 If you must do this, then force the use of a known-to-be-good backend
 (at the time of this writing, this includes only C<EVBACKEND_SELECT> and
 C<EVBACKEND_POLL>).
 
 the same underlying "file open").
 
 If you must do this, then force the use of a known-to-be-good backend
 (at the time of this writing, this includes only C<EVBACKEND_SELECT> and
 C<EVBACKEND_POLL>).
 

+Another thing you have to watch out for is that it is quite easy to
+receive "spurious" readyness notifications, that is your callback might
+be called with C<EV_READ> but a subsequent C<read>(2) will actually block
+because there is no data. Not only are some backends known to create a
+lot of those (for example solaris ports), it is very easy to get into
+this situation even with a relatively standard program structure. Thus
+it is best to always use non-blocking I/O: An extra C<read>(2) returning
+C<EAGAIN> is far preferable to a program hanging until some data arrives.
+
+If you cannot run the fd in non-blocking mode (for example you should not
+play around with an Xlib connection), then you have to seperately re-test
+wether a file descriptor is really ready with a known-to-be good interface
+such as poll (fortunately in our Xlib example, Xlib already does this on
+its own, so its quite safe to use).
+

 =over 4
 
 =item ev_io_init (ev_io *, callback, int fd, int events)
 
 =item ev_io_set (ev_io *, int fd, int events)
 
 =over 4
 
 =item ev_io_init (ev_io *, callback, int fd, int events)
 
 =item ev_io_set (ev_io *, int fd, int events)
 

-Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive
-events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ |
-EV_WRITE> to receive the given events.
-
-Please note that most of the more scalable backend mechanisms (for example
-epoll and solaris ports) can result in spurious readyness notifications
-for file descriptors, so you practically need to use non-blocking I/O (and
-treat callback invocation as hint only), or retest separately with a safe
-interface before doing I/O (XLib can do this), or force the use of either
-C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>, which don't suffer from this
-problem. Also note that it is quite easy to have your callback invoked
-when the readyness condition is no longer valid even when employing
-typical ways of handling events, so its a good idea to use non-blocking
-I/O unconditionally.
+Configures an C<ev_io> watcher. The C<fd> is the file descriptor to
+rceeive events for and events is either C<EV_READ>, C<EV_WRITE> or
+C<EV_READ | EV_WRITE> to receive the given events.

 
 =back
 
 
 =back
 


@@ -758,7 +765,7 @@ attempt to read a whole line in the callback:
   ev_loop (loop, 0);
 
 
   ev_loop (loop, 0);
 
 

-=head2 C<ev_timer> - relative and optionally recurring timeouts
+=head2 C<ev_timer> - relative and optionally repeating timeouts

 
 Timer watchers are simple relative timers that generate an event after a
 given time, and optionally repeating in regular intervals after that.
 
 Timer watchers are simple relative timers that generate an event after a
 given time, and optionally repeating in regular intervals after that.


@@ -850,7 +857,7 @@ inactivity.
   ev_timer_again (&mytimer);
 
 
   ev_timer_again (&mytimer);
 
 

-=head2 C<ev_periodic> - to cron or not to cron
+=head2 C<ev_periodic> - to cron or not to cron?

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


@@ -988,7 +995,7 @@ Example: call a callback every hour, starting now:
   ev_periodic_start (loop, &hourly_tick);
   
 
   ev_periodic_start (loop, &hourly_tick);
   
 

-=head2 C<ev_signal> - signal me when a signal gets signalled
+=head2 C<ev_signal> - signal me when a signal gets signalled!

 
 Signal watchers will trigger an event when the process receives a specific
 signal one or more times. Even though signals are very asynchronous, libev
 
 Signal watchers will trigger an event when the process receives a specific
 signal one or more times. Even though signals are very asynchronous, libev


@@ -1014,7 +1021,7 @@ of the C<SIGxxx> constants).
 =back
 
 
 =back
 
 

-=head2 C<ev_child> - wait for pid status changes
+=head2 C<ev_child> - watch out for process status changes

 
 Child watchers trigger when your process receives a SIGCHLD in response to
 some child status changes (most typically when a child of yours dies).
 
 Child watchers trigger when your process receives a SIGCHLD in response to
 some child status changes (most typically when a child of yours dies).


@@ -1047,7 +1054,7 @@ Example: try to exit cleanly on SIGINT and SIGTERM.
   ev_signal_start (loop, &sigint_cb);
 
 
   ev_signal_start (loop, &sigint_cb);
 
 

-=head2 C<ev_idle> - when you've got nothing better to do
+=head2 C<ev_idle> - when you've got nothing better to do...

 
 Idle watchers trigger events when there are no other events are pending
 (prepare, check and other idle watchers do not count). That is, as long
 
 Idle watchers trigger events when there are no other events are pending
 (prepare, check and other idle watchers do not count). That is, as long


@@ -1091,7 +1098,7 @@ callback, free it. Alos, use no error checking, as usual.
   ev_idle_start (loop, idle_cb);
 
 
   ev_idle_start (loop, idle_cb);
 
 

-=head2 C<ev_prepare> and C<ev_check> - customise your event loop
+=head2 C<ev_prepare> and C<ev_check> - customise your event loop!

 
 Prepare and check watchers are usually (but not always) used in tandem:
 prepare watchers get invoked before the process blocks and check watchers
 
 Prepare and check watchers are usually (but not always) used in tandem:
 prepare watchers get invoked before the process blocks and check watchers


@@ -1135,7 +1142,7 @@ macros, but using them is utterly, utterly and completely pointless.
 Example: *TODO*.
 
 
 Example: *TODO*.
 
 

-=head2 C<ev_embed> - when one backend isn't enough
+=head2 C<ev_embed> - when one backend isn't enough...

 
 This is a rather advanced watcher type that lets you embed one event loop
 into another (currently only C<ev_io> events are supported in the embedded
 
 This is a rather advanced watcher type that lets you embed one event loop
 into another (currently only C<ev_io> events are supported in the embedded


@@ -1464,14 +1471,14 @@ in your include path (e.g. in libev/ when using -Ilibev):
 
   ev_win32.c      required on win32 platforms only
 
 
   ev_win32.c      required on win32 platforms only
 

-  ev_select.c     only when select backend is enabled (which is is by default)
+  ev_select.c     only when select backend is enabled (which is by default)

   ev_poll.c       only when poll backend is enabled (disabled by default)
   ev_epoll.c      only when the epoll backend is enabled (disabled by default)
   ev_kqueue.c     only when the kqueue backend is enabled (disabled by default)
   ev_port.c       only when the solaris port backend is enabled (disabled by default)
 
 F<ev.c> includes the backend files directly when enabled, so you only need
   ev_poll.c       only when poll backend is enabled (disabled by default)
   ev_epoll.c      only when the epoll backend is enabled (disabled by default)
   ev_kqueue.c     only when the kqueue backend is enabled (disabled by default)
   ev_port.c       only when the solaris port backend is enabled (disabled by default)
 
 F<ev.c> includes the backend files directly when enabled, so you only need

-to compile a single file.
+to compile this single file.

 
 =head3 LIBEVENT COMPATIBILITY API
 
 
 =head3 LIBEVENT COMPATIBILITY API
 


@@ -1494,8 +1501,8 @@ You need the following additional files for this:
 
 Instead of using C<EV_STANDALONE=1> and providing your config in
 whatever way you want, you can also C<m4_include([libev.m4])> in your
 
 Instead of using C<EV_STANDALONE=1> and providing your config in
 whatever way you want, you can also C<m4_include([libev.m4])> in your

-F<configure.ac> and leave C<EV_STANDALONE> off. F<ev.c> will then include
-F<config.h> and configure itself accordingly.
+F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then
+include F<config.h> and configure itself accordingly.

 
 For this of course you need the m4 file:
 
 
 For this of course you need the m4 file:
 


@@ -1585,7 +1592,7 @@ backend for BSD and BSD-like systems, although on most BSDs kqueue only
 supports some types of fds correctly (the only platform we found that
 supports ptys for example was NetBSD), so kqueue might be compiled in, but
 not be used unless explicitly requested. The best way to use it is to find
 supports some types of fds correctly (the only platform we found that
 supports ptys for example was NetBSD), so kqueue might be compiled in, but
 not be used unless explicitly requested. The best way to use it is to find

-out wether kqueue supports your type of fd properly and use an embedded
+out whether kqueue supports your type of fd properly and use an embedded

 kqueue loop.
 
 =item EV_USE_PORT
 kqueue loop.
 
 =item EV_USE_PORT