[ViewVC] Diff of: cvs/EV/README

Comparing EV/README (file contents):
Revision 1.22 by root, Mon Jan 28 12:24:05 2008 UTC vs.
Revision 1.25 by root, Sun May 18 10:45:36 2008 UTC

 DESCRIPTION
     This module provides an interface to libev
     (<http://software.schmorp.de/pkg/libev.html>). While the documentation
     below is comprehensive, one might also consult the documentation of
-    libev itself (<http://cvs.schmorp.de/libev/ev.html>) for more subtle
+    libev itself (<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>)
-    details on watcher semantics or some discussion on the available
+    for more subtle details on watcher semantics or some discussion on the
-    backends, or how to force a specific backend with "LIBEV_FLAGS", or just
+    available backends, or how to force a specific backend with
-    about in any case because it has much more detailed information.
+    "LIBEV_FLAGS", or just about in any case because it has much more
+    detailed information.
+    This module is very fast and scalable. It is actually so fast that you
+    can use it through the AnyEvent module, stay portable to other event
+    loops (if you don't rely on any watcher types not available through it)
+    and still be faster than with any other event loop currently supported
+    in Perl.
 EVENT LOOPS
     EV supports multiple event loops: There is a single "default event loop"
     that can handle everything including signals and child watchers, and any
     number of "dynamic event loops" that can use different backends (with
             This time simply fires at the wallclock time $at and doesn't
             repeat. It will not adjust when a time jump occurs, that is, if
             it is to be run at January 1st 2011 then it will run when the
             system time reaches or surpasses this time.
-        *   non-repeating interval timer ($interval > 0, $reschedule_cb = 0)
+        *   repeating interval timer ($interval > 0, $reschedule_cb = 0)
             In this mode the watcher will always be scheduled to time out at
             the next "$at + N * $interval" time (for some integer N) and
             then repeat, regardless of any time jumps.
         managed automatically.
         The "embed_ns" variant doesn't start (activate) the newly created
         watcher.
+   ASYNC WATCHERS - how to wake up another event loop
+    Async watchers are provided by EV, but have little use in perl directly,
+    as perl neither supports threads nor direct access to signal handlers or
+    other contexts where they could be of value.
+    It is, however, possible to use them from the XS level.
+    Please see the libev documentation for further details.
+    $w = EV::async $callback
+    $w = EV::async_ns $callback
+    $w->send
+    $bool = $w->async_pending
 PERL SIGNALS
     While Perl signal handling (%SIG) is not affected by EV, the behaviour
     with EV is as the same as any other C library: Perl-signals will only be
     handled when Perl runs, which means your signal handler might be invoked
     only the next time an event callback is invoked.
     course.
 SEE ALSO
     EV::ADNS (asynchronous DNS), Glib::EV (makes Glib/Gtk2 use EV as event
     loop), EV::Glib (embed Glib into EV), Coro::EV (efficient coroutines
-    with EV), Net::SNMP::EV (asynchronous SNMP).
+    with EV), Net::SNMP::EV (asynchronous SNMP), AnyEvent for event-loop
+    agnostic and portable event driven programming.
 AUTHOR
      Marc Lehmann <schmorp@schmorp.de>
      http://home.schmorp.de/

Diff Legend

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

Comparing EV/README (file contents): Revision 1.22 by root, Mon Jan 28 12:24:05 2008 UTC vs. Revision 1.25 by root, Sun May 18 10:45:36 2008 UTC

Diff Legend

Comparing EV/README (file contents):
Revision 1.22 by root, Mon Jan 28 12:24:05 2008 UTC vs.
Revision 1.25 by root, Sun May 18 10:45:36 2008 UTC