[ViewVC] Diff of: cvs/AnyEvent/README

Comparing AnyEvent/README (file contents):
Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC vs.
Revision 1.55 by root, Mon Sep 14 05:05:09 2009 UTC

           after => 1,
           cb    => sub { $result_ready->send },
        );
        # this "blocks" (while handling events) till the callback
-       # calls -<send
+       # calls ->send
        $result_ready->recv;
     Example: wait for a timer, but take advantage of the fact that condition
     variables are also callable directly.
              warn "read: $input\n";       # output what has been read
              $cv->send if $input =~ /^q/i; # quit program if /^q/i
           },
        );
-       my $time_watcher; # can only be used once
-       sub new_timer {
-          $timer = AnyEvent->timer (after => 1, cb => sub {
+       my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
-             warn "timeout\n"; # print 'timeout' about every second
+          warn "timeout\n"; # print 'timeout' at most every second
-             &new_timer; # and restart the time
-          });
-       }
+       });
-       new_timer; # create first timer
        $cv->recv; # wait until user enters /^q/i
 REAL-WORLD EXAMPLE
     Consider the Net::FCP module. It features (among others) the following
     As you can see, the AnyEvent + EV combination even beats the
     hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
     backend easily beats IO::Lambda and POE.
     And even the 100% non-blocking version written using the high-level (and
-    slow :) AnyEvent::Handle abstraction beats both POE and IO::Lambda by a
+    slow :) AnyEvent::Handle abstraction beats both POE and IO::Lambda
-    large margin, even though it does all of DNS, tcp-connect and socket I/O
+    higher level ("unoptimised") abstractions by a large margin, even though
-    in a non-blocking way.
+    it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
     The two AnyEvent benchmarks programs can be found as eg/ae0.pl and
     eg/ae2.pl in the AnyEvent distribution, the remaining benchmarks are
-    part of the IO::lambda distribution and were used without any changes.
+    part of the IO::Lambda distribution and were used without any changes.
 SIGNALS
     AnyEvent currently installs handlers for these signals:
     SIGCHLD
         "AnyEvent::Util::guard". This speeds up guards considerably (and
         uses a lot less memory), but otherwise doesn't affect guard
         operation much. It is purely used for performance.
     JSON and JSON::XS
-        This module is required when you want to read or write JSON data via
+        One of these modules is required when you want to read or write JSON
-        AnyEvent::Handle. It is also written in pure-perl, but can take
+        data via AnyEvent::Handle. It is also written in pure-perl, but can
-        advantage of the ultra-high-speed JSON::XS module when it is
+        take advantage of the ultra-high-speed JSON::XS module when it is
         installed.
         In fact, AnyEvent::Handle will use JSON::XS by default if it is
         installed.

Diff Legend

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

Comparing AnyEvent/README (file contents): Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC vs. Revision 1.55 by root, Mon Sep 14 05:05:09 2009 UTC

Diff Legend

Comparing AnyEvent/README (file contents):
Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC vs.
Revision 1.55 by root, Mon Sep 14 05:05:09 2009 UTC