[ViewVC] Diff of: cvs/AnyEvent/README

Comparing AnyEvent/README (file contents):
Revision 1.62 by root, Sun Jun 6 10:13:57 2010 UTC vs.
Revision 1.63 by root, Wed Oct 13 19:49:46 2010 UTC

        # file handle or descriptor readable
        my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ...  });
        # one-shot or repeating timers
        my $w = AnyEvent->timer (after => $seconds, cb => sub { ...  });
-       my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
+       my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
        print AnyEvent->now;  # prints current event loop time
        print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
        # POSIX signal
     This manpage is mainly a reference manual. If you are interested in a
     tutorial or some gentle introduction, have a look at the AnyEvent::Intro
     manpage.
 SUPPORT
+    An FAQ document is available as AnyEvent::FAQ.
-    There is a mailinglist for discussing all things AnyEvent, and an IRC
+    There also is a mailinglist for discussing all things AnyEvent, and an
-    channel, too.
+    IRC channel, too.
     See the AnyEvent project page at the Schmorpforge Ta-Sa Software
     Repository, at <http://anyevent.schmorp.de>, for more info.
 WHY YOU SHOULD USE THIS MODULE (OR NOT)
     module users into the same thing by forcing them to use the same event
     model you use.
     For modules like POE or IO::Async (which is a total misnomer as it is
     actually doing all I/O *synchronously*...), using them in your module is
-    like joining a cult: After you joined, you are dependent on them and you
+    like joining a cult: After you join, you are dependent on them and you
     cannot use anything else, as they are simply incompatible to everything
     that isn't them. What's worse, all the potential users of your module
     are *also* forced to use the same event loop you use.
     AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
     fine. AnyEvent + Tk works fine etc. etc. but none of these work together
     with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if your
     module uses one of those, every user of your module has to use it, too.
     But if your module uses AnyEvent, it works transparently with all event
     models it supports (including stuff like IO::Async, as long as those use
-    one of the supported event loops. It is trivial to add new event loops
+    one of the supported event loops. It is easy to add new event loops to
-    to AnyEvent, too, so it is future-proof).
+    AnyEvent, too, so it is future-proof).
     In addition to being free of having to use *the one and only true event
     model*, AnyEvent also is free of bloat and policy: with POE or similar
     modules, you get an enormous amount of code and strict rules you have to
-    follow. AnyEvent, on the other hand, is lean and up to the point, by
+    follow. AnyEvent, on the other hand, is lean and to the point, by only
-    only offering the functionality that is necessary, in as thin as a
+    offering the functionality that is necessary, in as thin as a wrapper as
-    wrapper as technically possible.
+    technically possible.
     Of course, AnyEvent comes with a big (and fully optional!) toolbox of
     useful functionality, such as an asynchronous DNS resolver, 100%
     non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms
     such as Windows) and lots of real-world knowledge and workarounds for
     Now, if you *do want* lots of policy (this can arguably be somewhat
     useful) and you want to force your users to use the one and only event
     model, you should *not* use this module.
 DESCRIPTION
-    AnyEvent provides an identical interface to multiple event loops. This
+    AnyEvent provides a uniform interface to various event loops. This
-    allows module authors to utilise an event loop without forcing module
+    allows module authors to use event loop functionality without forcing
-    users to use the same event loop (as only a single event loop can
+    module users to use a specific event loop implementation (since more
-    coexist peacefully at any one time).
+    than one event loop cannot coexist peacefully).
     The interface itself is vaguely similar, but not identical to the Event
     module.
     During the first call of any watcher-creation method, the module tries
     to detect the currently loaded event loop by probing whether one of the
-    following modules is already loaded: EV, Event, Glib,
+    following modules is already loaded: EV, AnyEvent::Impl::Perl, Event,
-    AnyEvent::Impl::Perl, Tk, Event::Lib, Qt, POE. The first one found is
+    Glib, Tk, Event::Lib, Qt, POE. The first one found is used. If none are
-    used. If none are found, the module tries to load these modules
+    detected, the module tries to load the first four modules in the order
-    (excluding Tk, Event::Lib, Qt and POE as the pure perl adaptor should
+    given; but note that if EV is not available, the pure-perl
-    always succeed) in the order given. The first one that can be
+    AnyEvent::Impl::Perl should always work, so the other two are not
-    successfully loaded will be used. If, after this, still none could be
+    normally tried.
-    found, AnyEvent will fall back to a pure-perl event loop, which is not
-    very efficient, but should work everywhere.
     Because AnyEvent first checks for modules that are already loaded,
     loading an event model explicitly before first using AnyEvent will
     likely make that model the default. For example:
        use AnyEvent;
        # .. AnyEvent will likely default to Tk
     The *likely* means that, if any module loads another event model and
-    starts using it, all bets are off. Maybe you should tell their authors
+    starts using it, all bets are off - this case should be very rare
-    to use AnyEvent so their modules work together with others seamlessly...
+    though, as very few modules hardcode event loops without announcing this
+    very loudly.
     The pure-perl implementation of AnyEvent is called
     "AnyEvent::Impl::Perl". Like other event modules you can load it
     explicitly and enjoy the high availability of that event loop :)
     callback when the event occurs (of course, only when the event model is
     in control).
     Note that callbacks must not permanently change global variables
     potentially in use by the event loop (such as $_ or $[) and that
-    callbacks must not "die". The former is good programming practise in
+    callbacks must not "die". The former is good programming practice in
     Perl and the latter stems from the fact that exception handling differs
     widely between event loops.
-    To disable the watcher you have to destroy it (e.g. by setting the
+    To disable a watcher you have to destroy it (e.g. by setting the
     variable you store it in to "undef" or otherwise deleting all references
     to it).
     All watchers are created by calling a method on the "AnyEvent" class.
     Many watchers either are used with "recursion" (repeating timers for
     example), or need to refer to their watcher object in other ways.
-    An any way to achieve that is this pattern:
+    One way to achieve that is this pattern:
        my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
           # you can use $w here, for example to undef it
           undef $w;
        });
     The I/O watcher might use the underlying file descriptor or a copy of
     it. You must not close a file handle as long as any watcher is active on
     the underlying file descriptor.
-    Some event loops issue spurious readyness notifications, so you should
+    Some event loops issue spurious readiness notifications, so you should
     always use non-blocking calls when reading/writing from/to your file
     handles.
     Example: wait for readability of STDIN, then read a line and disable the
     watcher.
     Although the callback might get passed parameters, their value and
     presence is undefined and you cannot rely on them. Portable AnyEvent
     callbacks cannot use arguments passed to time watcher callbacks.
-    The callback will normally be invoked once only. If you specify another
+    The callback will normally be invoked only once. If you specify another
     parameter, "interval", as a strictly positive number (> 0), then the
     callback will be invoked regularly at that interval (in fractional
     seconds) after the first invocation. If "interval" is specified with a
-    false value, then it is treated as if it were missing.
+    false value, then it is treated as if it were not specified at all.
     The callback will be rescheduled before invoking the callback, but no
-    attempt is done to avoid timer drift in most backends, so the interval
+    attempt is made to avoid timer drift in most backends, so the interval
     is only approximate.
     Example: fire an event after 7.7 seconds.
        my $w = AnyEvent->timer (after => 7.7, cb => sub {
     While most event loops expect timers to specified in a relative way,
     they use absolute time internally. This makes a difference when your
     clock "jumps", for example, when ntp decides to set your clock backwards
     from the wrong date of 2014-01-01 to 2008-01-01, a watcher that is
-    supposed to fire "after" a second might actually take six years to
+    supposed to fire "after a second" might actually take six years to
     finally fire.
     AnyEvent cannot compensate for this. The only event loop that is
-    conscious about these issues is EV, which offers both relative
+    conscious of these issues is EV, which offers both relative (ev_timer,
-    (ev_timer, based on true relative time) and absolute (ev_periodic, based
+    based on true relative time) and absolute (ev_periodic, based on
-    on wallclock time) timers.
+    wallclock time) timers.
     AnyEvent always prefers relative timers, if available, matching the
     AnyEvent API.
     AnyEvent has two additional methods that return the "current time":
         *In almost all cases (in all cases if you don't care), this is the
         function to call when you want to know the current time.*
         This function is also often faster then "AnyEvent->time", and thus
         the preferred method if you want some timestamp (for example,
-        AnyEvent::Handle uses this to update it's activity timeouts).
+        AnyEvent::Handle uses this to update its activity timeouts).
         The rest of this section is only of relevance if you try to be very
-        exact with your timing, you can skip it without bad conscience.
+        exact with your timing; you can skip it without a bad conscience.
         For a practical example of when these times differ, consider
         Event::Lib and EV and the following set-up:
-        The event loop is running and has just invoked one of your callback
+        The event loop is running and has just invoked one of your callbacks
         at time=500 (assume no other callbacks delay processing). In your
         callback, you wait a second by executing "sleep 1" (blocking the
         process for a second) and then (at time=501) you create a relative
         timer that fires after three seconds.
    Signal Races, Delays and Workarounds
     Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
     callbacks to signals in a generic way, which is a pity, as you cannot do
     race-free signal handling in perl, requiring C libraries for this.
-    AnyEvent will try to do it's best, which means in some cases, signals
+    AnyEvent will try to do its best, which means in some cases, signals
     will be delayed. The maximum time a signal might be delayed is specified
     in $AnyEvent::MAX_SIGNAL_LATENCY (default: 10 seconds). This variable
     can be changed only before the first signal watcher is created, and
     should be left alone otherwise. This variable determines how often
     AnyEvent polls for signals (in case a wake-up was missed). Higher values
     saving.
     All these problems can be avoided by installing the optional
     Async::Interrupt module, which works with most event loops. It will not
     work with inherently broken event loops such as Event or Event::Lib (and
-    not with POE currently, as POE does it's own workaround with one-second
+    not with POE currently, as POE does its own workaround with one-second
     latency). For those, you just have to suffer the delays.
   CHILD PROCESS WATCHERS
        $w = AnyEvent->child (pid => <process id>, cb => <callback>);
-    You can also watch on a child process exit and catch its exit status.
+    You can also watch for a child process exit and catch its exit status.
-    The child process is specified by the "pid" argument (one some backends,
+    The child process is specified by the "pid" argument (on some backends,
     using 0 watches for any child process exit, on others this will croak).
     The watcher will be triggered only when the child process has finished
     and an exit status is available, not on any trace events
     (stopped/continued).
        $done->recv;
   IDLE WATCHERS
        $w = AnyEvent->idle (cb => <callback>);
-    Repeatedly invoke the callback after the process becomes idle, until
+    This will repeatedly invoke the callback after the process becomes idle,
-    either the watcher is destroyed or new events have been detected.
+    until either the watcher is destroyed or new events have been detected.
     Idle watchers are useful when there is a need to do something, but it is
     not so important (or wise) to do it instantly. The callback will be
     invoked only when there is "nothing better to do", which is usually
     defined as "all outstanding events have been handled and no new events
         called when the signal fires.
     *   Condition variables are like "Merge Points" - points in your program
         where you merge multiple independent results/control flows into one.
-    *   Condition variables represent a transaction - function that start
+    *   Condition variables represent a transaction - functions that start
         some kind of transaction can return them, leaving the caller the
         choice between waiting in a blocking fashion, or setting a callback.
     *   Condition variables represent future values, or promises to deliver
         some result, long before the result is available.
     Condition variables are represented by hash refs in perl, and the keys
     used by AnyEvent itself are all named "_ae_XXX" to make subclassing easy
     (it is often useful to build your own transaction class on top of
     AnyEvent). To subclass, use "AnyEvent::CondVar" as base class and call
-    it's "new" method in your own "new" method.
+    its "new" method in your own "new" method.
     There are two "sides" to a condition variable - the "producer side"
     which eventually calls "-> send", and the "consumer side", which waits
     for the send to occur.
         Condition variables are overloaded so one can call them directly (as
         if they were a code reference). Calling them directly is the same as
         calling "send".
     $cv->croak ($error)
-        Similar to send, but causes all call's to "->recv" to invoke
+        Similar to send, but causes all calls to "->recv" to invoke
         "Carp::croak" with the given error message/object/scalar.
         This can be used to signal any errors to the condition variable
         user/consumer. Doing it this way instead of calling "croak" directly
-        delays the error detetcion, but has the overwhelmign advantage that
+        delays the error detection, but has the overwhelming advantage that
         it diagnoses the error at the place where the result is expected,
-        and not deep in some event clalback without connection to the actual
+        and not deep in some event callback with no connection to the actual
         code causing the problem.
     $cv->begin ([group callback])
     $cv->end
         These two methods can be used to combine many transactions/events
         there is one call to "begin", so the condvar waits for all calls to
         "end" before sending.
         The ping example mentioned above is slightly more complicated, as
         the there are results to be passwd back, and the number of tasks
-        that are begung can potentially be zero:
+        that are begun can potentially be zero:
            my $cv = AnyEvent->condvar;
            my %result;
            $cv->begin (sub { shift->send (\%result) });
         callback to be called once the counter reaches 0, and second, it
         ensures that "send" is called even when "no" hosts are being pinged
         (the loop doesn't execute once).
         This is the general pattern when you "fan out" into multiple (but
-        potentially none) subrequests: use an outer "begin"/"end" pair to
+        potentially zero) subrequests: use an outer "begin"/"end" pair to
         set the callback and ensure "end" is called at least once, and then,
         for each subrequest you start, call "begin" and for each subrequest
         you finish, call "end".
    METHODS FOR CONSUMERS
     These methods should only be used by the consuming side, i.e. the code
     awaits the condition.
     $cv->recv
         Wait (blocking if necessary) until the "->send" or "->croak" methods
-        have been called on c<$cv>, while servicing other watchers normally.
+        have been called on $cv, while servicing other watchers normally.
         You can only wait once on a condition - additional calls are valid
         but will return immediately.
         If an error condition has been set by calling "->croak", then this
         example, by coupling condition variables with some kind of request
         results and supporting callbacks so the caller knows that getting
         the result will not block, while still supporting blocking waits if
         the caller so desires).
-        You can ensure that "-recv" never blocks by setting a callback and
+        You can ensure that "->recv" never blocks by setting a callback and
         only calling "->recv" from within that callback (or at a later
         time). This will work even when the event loop does not support
         blocking waits otherwise.
     $bool = $cv->ready
     $cb = $cv->cb ($cb->($cv))
         This is a mutator function that returns the callback set and
         optionally replaces it before doing so.
-        The callback will be called when the condition becomes (or already
+        The callback will be called when the condition becomes "true", i.e.
-        was) "true", i.e. when "send" or "croak" are called (or were
+        when "send" or "croak" are called, with the only argument being the
-        called), with the only argument being the condition variable itself.
+        condition variable itself. If the condition is already true, the
-        Calling "recv" inside the callback or at any later time is
+        callback is called immediately when it is set. Calling "recv" inside
-        guaranteed not to block.
+        the callback or at any later time is guaranteed not to block.
 SUPPORTED EVENT LOOPS/BACKENDS
     The available backend classes are (every class has its own manpage):
     Backends that are autoprobed when no other event loop can be found.
            AnyEvent::Impl::EV        based on EV (interface to libev, best choice).
            AnyEvent::Impl::Perl      pure-perl implementation, fast and portable.
     Backends that are transparently being picked up when they are used.
-        These will be used when they are currently loaded when the first
+        These will be used if they are already loaded when the first watcher
-        watcher is created, in which case it is assumed that the application
+        is created, in which case it is assumed that the application is
-        is using them. This means that AnyEvent will automatically pick the
+        using them. This means that AnyEvent will automatically pick the
         right backend when the main program loads an event module before
         anything starts to create watchers. Nothing special needs to be done
         by the main program.
            AnyEvent::Impl::Event     based on Event, very stable, few glitches.
         Support for IO::Async can only be partial, as it is too broken and
         architecturally limited to even support the AnyEvent API. It also is
         the only event loop that needs the loop to be set explicitly, so it
         can only be used by a main program knowing about AnyEvent. See
-        AnyEvent::Impl::Async for the gory details.
+        AnyEvent::Impl::IOAsync for the gory details.
            AnyEvent::Impl::IOAsync   based on IO::Async, cannot be autoprobed.
     Event loops that are indirectly supported via other backends.
         Some event loops can be supported via other modules:
         Contains "undef" until the first watcher is being created, before
         the backend has been autodetected.
         Afterwards it contains the event model that is being used, which is
         the name of the Perl class implementing the model. This class is
-        usually one of the "AnyEvent::Impl:xxx" modules, but can be any
+        usually one of the "AnyEvent::Impl::xxx" modules, but can be any
         other class in the case AnyEvent has been extended at runtime (e.g.
         in *rxvt-unicode* it will be "urxvt::anyevent").
     AnyEvent::detect
         Returns $AnyEvent::MODEL, forcing autodetection of the event model
         if necessary. You should only call this function right before you
         would have created an AnyEvent watcher anyway, that is, as late as
-        possible at runtime, and not e.g. while initialising of your module.
+        possible at runtime, and not e.g. during initialisation of your
+        module.
         If you need to do some initialisation before AnyEvent watchers are
         created, use "post_detect".
     $guard = AnyEvent::post_detect { BLOCK }
         Arranges for the code block to be executed as soon as the event
-        model is autodetected (or immediately if this has already happened).
+        model is autodetected (or immediately if that has already happened).
         The block will be executed *after* the actual backend has been
         detected ($AnyEvent::MODEL is set), but *before* any watchers have
         been created, so it is possible to e.g. patch @AnyEvent::ISA or do
         other initialisations - see the sources of AnyEvent::Strict or
         object that automatically removes the callback again when it is
         destroyed (or "undef" when the hook was immediately executed). See
         AnyEvent::AIO for a case where this is useful.
         Example: Create a watcher for the IO::AIO module and store it in
-        $WATCHER. Only do so after the event loop is initialised, though.
+        $WATCHER, but do so only do so after the event loop is initialised.
            our WATCHER;
            my $guard = AnyEvent::post_detect {
               $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
            $WATCHER ||= $guard;
     @AnyEvent::post_detect
         If there are any code references in this array (you can "push" to it
-        before or after loading AnyEvent), then they will called directly
+        before or after loading AnyEvent), then they will be called directly
         after the event loop has been chosen.
         You should check $AnyEvent::MODEL before adding to this array,
         though: if it is defined then the event loop has already been
         detected, and the array will be ignored.
     stall the whole program, and the whole point of using events is to stay
     interactive.
     It is fine, however, to call "->recv" when the user of your module
     requests it (i.e. if you create a http request object ad have a method
-    called "results" that returns the results, it should call "->recv"
+    called "results" that returns the results, it may call "->recv" freely,
-    freely, as the user of your module knows what she is doing. always).
+    as the user of your module knows what she is doing. Always).
 WHAT TO DO IN THE MAIN PROGRAM
     There will always be a single main program - the only place that should
     dictate which event model to use.
-    If it doesn't care, it can just "use AnyEvent" and use it itself, or not
+    If the program is not event-based, it need not do anything special, even
-    do anything special (it does not need to be event-based) and let
+    when it depends on a module that uses an AnyEvent. If the program itself
-    AnyEvent decide which implementation to chose if some module relies on
+    uses AnyEvent, but does not care which event loop is used, all it needs
-    it.
+    to do is "use AnyEvent". In either case, AnyEvent will choose the best
+    available loop implementation.
     If the main program relies on a specific event model - for example, in
     Gtk2 programs you have to rely on the Glib module - you should load the
     event module before loading AnyEvent or any module that uses it:
     generally speaking, you should load it as early as possible. The reason
     is that modules might create watchers when they are loaded, and AnyEvent
     will decide on the event model to use as soon as it creates watchers,
-    and it might chose the wrong one unless you load the correct one
+    and it might choose the wrong one unless you load the correct one
     yourself.
     You can chose to use a pure-perl implementation by loading the
     "AnyEvent::Impl::Perl" module, which gives you similar behaviour
     everywhere, but letting AnyEvent chose the model is generally better.
     AnyEvent as a client and can therefore be mixed easily with other
     AnyEvent modules and other event loops in the same program. Some of the
     modules come as part of AnyEvent, the others are available via CPAN.
     AnyEvent::Util
-        Contains various utility functions that replace often-used but
+        Contains various utility functions that replace often-used blocking
-        blocking functions such as "inet_aton" by event-/callback-based
+        functions such as "inet_aton" with event/callback-based versions.
-        versions.
     AnyEvent::Socket
         Provides various utility functions for (internet protocol) sockets,
         addresses and name resolution. Also functions to create non-blocking
         tcp connections or tcp servers, with IPv6 and SRV record support and
         more.
     AnyEvent::Handle
         Provide read and write buffers, manages watchers for reads and
         writes, supports raw and formatted I/O, I/O queued and fully
-        transparent and non-blocking SSL/TLS (via AnyEvent::TLS.
+        transparent and non-blocking SSL/TLS (via AnyEvent::TLS).
     AnyEvent::DNS
         Provides rich asynchronous DNS resolver capabilities.
     AnyEvent::HTTP, AnyEvent::IRC, AnyEvent::XMPP, AnyEvent::GPSD,
     AnyEvent::Handle::UDP
         Here be danger!
         As Pauli would put it, "Not only is it not right, it's not even
         wrong!" - there are so many things wrong with AnyEvent::Handle::UDP,
-        most notably it's use of a stream-based API with a protocol that
+        most notably its use of a stream-based API with a protocol that
         isn't streamable, that the only way to improve it is to delete it.
         It features data corruption (but typically only under load) and
         general confusion. On top, the author is not only clueless about UDP
         but also fact-resistant - some gems of his understanding: "connect
         doesn't even understand what's wrong with his module when it is
         explained to him.
     AnyEvent::DBI
         Executes DBI requests asynchronously in a proxy process for you,
-        notifying you in an event-bnased way when the operation is finished.
+        notifying you in an event-based way when the operation is finished.
     AnyEvent::AIO
         Truly asynchronous (as opposed to non-blocking) I/O, should be in
         the toolbox of every event programmer. AnyEvent::AIO transparently
         fuses IO::AIO and AnyEvent together, giving AnyEvent access to
         thoroughly check the arguments passed to most method calls. If it
         finds any problems, it will croak.
         In other words, enables "strict" mode.
-        Unlike "use strict" (or it's modern cousin, "use common::sense", it
+        Unlike "use strict" (or its modern cousin, "use common::sense", it
         is definitely recommended to keep it off in production. Keeping
         "PERL_ANYEVENT_STRICT=1" in your environment while developing
         programs can be very useful, however.
     "PERL_ANYEVENT_MODEL"
         Feel free to install your own handler, or reset it to defaults.
 RECOMMENDED/OPTIONAL MODULES
     One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
-    it's built-in modules) are required to use it.
+    its built-in modules) are required to use it.
     That does not mean that AnyEvent won't take advantage of some additional
     modules if they are installed.
     This section explains which additional modules will be used, and how
         worthwhile: If this module is installed, then AnyEvent::Handle (with
         the help of AnyEvent::TLS), gains the ability to do TLS/SSL.
     Time::HiRes
         This module is part of perl since release 5.008. It will be used
-        when the chosen event library does not come with a timing source on
+        when the chosen event library does not come with a timing source of
-        it's own. The pure-perl event loop (AnyEvent::Impl::Perl) will
+        its own. The pure-perl event loop (AnyEvent::Impl::Perl) will
         additionally use it to try to use a monotonic clock for timing
         stability.
 FORK
     Most event libraries are not fork-safe. The ones who are usually are
     5.10 and check wether the leaks still show up. (Perl 5.10.0 has other
     annoying memleaks, such as leaking on "map" and "grep" but it is usually
     not as pronounced).
 SEE ALSO
+    Tutorial/Introduction: AnyEvent::Intro.
+    FAQ: AnyEvent::FAQ.
     Utility functions: AnyEvent::Util.
     Event modules: EV, EV::Glib, Glib::EV, Event, Glib::Event, Glib, Tk,
     Event::Lib, Qt, POE.
     Non-blocking file handles, sockets, TCP clients and servers:
     AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS.
     Asynchronous DNS: AnyEvent::DNS.
-    Coroutine support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event,
+    Thread support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event.
-    Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::XMPP,
+    Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::IRC,
     AnyEvent::HTTP.
 AUTHOR
        Marc Lehmann <schmorp@schmorp.de>
        http://home.schmorp.de/

Diff Legend

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

Comparing AnyEvent/README (file contents): Revision 1.62 by root, Sun Jun 6 10:13:57 2010 UTC vs. Revision 1.63 by root, Wed Oct 13 19:49:46 2010 UTC

Diff Legend

Comparing AnyEvent/README (file contents):
Revision 1.62 by root, Sun Jun 6 10:13:57 2010 UTC vs.
Revision 1.63 by root, Wed Oct 13 19:49:46 2010 UTC