From 2e79dc15d2fba4b69c8f62c2bf08a0899a3c578d Mon Sep 17 00:00:00 2001 From: root Date: Mon, 12 Nov 2007 19:20:05 +0000 Subject: *** empty log message *** --- ev.html | 23 +++++++++++++++++++---- ev.pod | 29 ++++++++++++++++++++++++++--- 2 files changed, 45 insertions(+), 7 deletions(-) diff --git a/ev.html b/ev.html index b5cb9f4..34a22df 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -451,8 +451,8 @@ 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 -to the same file/socket etc. description (that is, they share the same -underlying "file open").

+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 EVMETHOD_SELECT and EVMETHOD_POLL).

@@ -765,7 +765,22 @@ the given events it.

LIBEVENT EMULATION

Top

-

TBD.

+

Libev offers a compatibility emulation layer for libevent. It cannot +emulate the internals of libevent, so here are some usage hints:

+
+
* Use it by including <event.h>, as usual.
+
* The following members are fully supported: ev_base, ev_callback, +ev_arg, ev_fd, ev_res, ev_events.
+
* Avoid using ev_flags and the EVLIST_*-macros, while it is +maintained by libev, it does not work exactly the same way as in libevent (consider +it a private API).
+
* Priorities are not currently supported. Initialising priorities +will fail and all watchers will have the same priority, even though there +is an ev_pri field.
+
* Other members are not supported.
+
* The libev emulation is not ABI compatible to libevent, you need +to use the libev header file and library.
+

C++ SUPPORT

Top

diff --git a/ev.pod b/ev.pod index a3bcef3..616fea2 100644 --- a/ev.pod +++ b/ev.pod @@ -427,8 +427,8 @@ 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 -to the same file/socket etc. description (that is, they share the same -underlying "file open"). +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 EVMETHOD_SELECT and @@ -774,7 +774,30 @@ Feed an event as if the given signal occured (loop must be the default loop!). =head1 LIBEVENT EMULATION -TBD. +Libev offers a compatibility emulation layer for libevent. It cannot +emulate the internals of libevent, so here are some usage hints: + +=over 4 + +=item * Use it by including , as usual. + +=item * The following members are fully supported: ev_base, ev_callback, +ev_arg, ev_fd, ev_res, ev_events. + +=item * Avoid using ev_flags and the EVLIST_*-macros, while it is +maintained by libev, it does not work exactly the same way as in libevent (consider +it a private API). + +=item * Priorities are not currently supported. Initialising priorities +will fail and all watchers will have the same priority, even though there +is an ev_pri field. + +=item * Other members are not supported. + +=item * The libev emulation is I ABI compatible to libevent, you need +to use the libev header file and library. + +=back =head1 C++ SUPPORT -- cgit v1.2.3