ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.189 by root, Mon Nov 3 21:49:25 2008 UTC vs.
Revision 1.253 by root, Tue Jul 21 06:00:47 2009 UTC

1=head1 NAME 1=head1 NAME
2 2
3AnyEvent - provide framework for multiple event loops 3AnyEvent - events independent of event loop implementation
4 4
5EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops 5EV, Event, Glib, Tk, Perl, Event::Lib, Qt and POE are various supported
6event loops.
6 7
7=head1 SYNOPSIS 8=head1 SYNOPSIS
8 9
9 use AnyEvent; 10 use AnyEvent;
10 11
12 # file descriptor readable
11 my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { ... }); 13 my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
12 14
15 # one-shot or repeating timers
13 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... }); 16 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
14 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ... 17 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
15 18
16 print AnyEvent->now; # prints current event loop time 19 print AnyEvent->now; # prints current event loop time
17 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time. 20 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
18 21
22 # POSIX signal
19 my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... }); 23 my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
20 24
25 # child process exit
21 my $w = AnyEvent->child (pid => $pid, cb => sub { 26 my $w = AnyEvent->child (pid => $pid, cb => sub {
22 my ($pid, $status) = @_; 27 my ($pid, $status) = @_;
23 ... 28 ...
24 }); 29 });
30
31 # called when event loop idle (if applicable)
32 my $w = AnyEvent->idle (cb => sub { ... });
25 33
26 my $w = AnyEvent->condvar; # stores whether a condition was flagged 34 my $w = AnyEvent->condvar; # stores whether a condition was flagged
27 $w->send; # wake up current and all future recv's 35 $w->send; # wake up current and all future recv's
28 $w->recv; # enters "main loop" till $condvar gets ->send 36 $w->recv; # enters "main loop" till $condvar gets ->send
29 # use a condvar in callback mode: 37 # use a condvar in callback mode:
32=head1 INTRODUCTION/TUTORIAL 40=head1 INTRODUCTION/TUTORIAL
33 41
34This manpage is mainly a reference manual. If you are interested 42This manpage is mainly a reference manual. If you are interested
35in a tutorial or some gentle introduction, have a look at the 43in a tutorial or some gentle introduction, have a look at the
36L<AnyEvent::Intro> manpage. 44L<AnyEvent::Intro> manpage.
45
46=head1 SUPPORT
47
48There is a mailinglist for discussing all things AnyEvent, and an IRC
49channel, too.
50
51See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
52Respository>, at L<http://anyevent.schmorp.de>, for more info.
37 53
38=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) 54=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
39 55
40Glib, POE, IO::Async, Event... CPAN offers event models by the dozen 56Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
41nowadays. So what is different about AnyEvent? 57nowadays. So what is different about AnyEvent?
137These watchers are normal Perl objects with normal Perl lifetime. After 153These watchers are normal Perl objects with normal Perl lifetime. After
138creating a watcher it will immediately "watch" for events and invoke the 154creating a watcher it will immediately "watch" for events and invoke the
139callback when the event occurs (of course, only when the event model 155callback when the event occurs (of course, only when the event model
140is in control). 156is in control).
141 157
158Note that B<callbacks must not permanently change global variables>
159potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
160callbacks must not C<die> >>. The former is good programming practise in
161Perl and the latter stems from the fact that exception handling differs
162widely between event loops.
163
142To disable the watcher you have to destroy it (e.g. by setting the 164To disable the watcher you have to destroy it (e.g. by setting the
143variable you store it in to C<undef> or otherwise deleting all references 165variable you store it in to C<undef> or otherwise deleting all references
144to it). 166to it).
145 167
146All watchers are created by calling a method on the C<AnyEvent> class. 168All watchers are created by calling a method on the C<AnyEvent> class.
162=head2 I/O WATCHERS 184=head2 I/O WATCHERS
163 185
164You can create an I/O watcher by calling the C<< AnyEvent->io >> method 186You can create an I/O watcher by calling the C<< AnyEvent->io >> method
165with the following mandatory key-value pairs as arguments: 187with the following mandatory key-value pairs as arguments:
166 188
167C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events 189C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
168(AnyEvent might or might not keep a reference to this file handle). C<poll> 190for events (AnyEvent might or might not keep a reference to this file
191handle). Note that only file handles pointing to things for which
192non-blocking operation makes sense are allowed. This includes sockets,
193most character devices, pipes, fifos and so on, but not for example files
194or block devices.
195
169must be a string that is either C<r> or C<w>, which creates a watcher 196C<poll> must be a string that is either C<r> or C<w>, which creates a
170waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the 197watcher waiting for "r"eadable or "w"ritable events, respectively.
198
171callback to invoke each time the file handle becomes ready. 199C<cb> is the callback to invoke each time the file handle becomes ready.
172 200
173Although the callback might get passed parameters, their value and 201Although the callback might get passed parameters, their value and
174presence is undefined and you cannot rely on them. Portable AnyEvent 202presence is undefined and you cannot rely on them. Portable AnyEvent
175callbacks cannot use arguments passed to I/O watcher callbacks. 203callbacks cannot use arguments passed to I/O watcher callbacks.
176 204
308In either case, if you care (and in most cases, you don't), then you 336In either case, if you care (and in most cases, you don't), then you
309can get whatever behaviour you want with any event loop, by taking the 337can get whatever behaviour you want with any event loop, by taking the
310difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into 338difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
311account. 339account.
312 340
341=item AnyEvent->now_update
342
343Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache
344the current time for each loop iteration (see the discussion of L<<
345AnyEvent->now >>, above).
346
347When a callback runs for a long time (or when the process sleeps), then
348this "current" time will differ substantially from the real time, which
349might affect timers and time-outs.
350
351When this is the case, you can call this method, which will update the
352event loop's idea of "current time".
353
354Note that updating the time I<might> cause some events to be handled.
355
313=back 356=back
314 357
315=head2 SIGNAL WATCHERS 358=head2 SIGNAL WATCHERS
316 359
317You can watch for signals using a signal watcher, C<signal> is the signal 360You can watch for signals using a signal watcher, C<signal> is the signal
326invocation, and callback invocation will be synchronous. Synchronous means 369invocation, and callback invocation will be synchronous. Synchronous means
327that it might take a while until the signal gets handled by the process, 370that it might take a while until the signal gets handled by the process,
328but it is guaranteed not to interrupt any other callbacks. 371but it is guaranteed not to interrupt any other callbacks.
329 372
330The main advantage of using these watchers is that you can share a signal 373The main advantage of using these watchers is that you can share a signal
331between multiple watchers. 374between multiple watchers, and AnyEvent will ensure that signals will not
375interrupt your program at bad times.
332 376
333This watcher might use C<%SIG>, so programs overwriting those signals 377This watcher might use C<%SIG> (depending on the event loop used),
334directly will likely not work correctly. 378so programs overwriting those signals directly will likely not work
379correctly.
335 380
336Example: exit on SIGINT 381Example: exit on SIGINT
337 382
338 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); 383 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
384
385=head3 Signal Races, Delays and Workarounds
386
387Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
388callbacks to signals in a generic way, which is a pity, as you cannot do
389race-free signal handling in perl. AnyEvent will try to do it's best, but
390in some cases, signals will be delayed. The maximum time a signal might
391be delayed is specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10
392seconds). This variable can be changed only before the first signal
393watcher is created, and should be left alone otherwise. Higher values
394will cause fewer spurious wake-ups, which is better for power and CPU
395saving. All these problems can be avoided by installing the optional
396L<Async::Interrupt> module. This will not work with inherently broken
397event loops such as L<Event> or L<Event::Lib> (and not with L<POE>
398currently, as POE does it's own workaround with one-second latency). With
399those, you just have to suffer the delays.
339 400
340=head2 CHILD PROCESS WATCHERS 401=head2 CHILD PROCESS WATCHERS
341 402
342You can also watch on a child process exit and catch its exit status. 403You can also watch on a child process exit and catch its exit status.
343 404
357 418
358There is a slight catch to child watchers, however: you usually start them 419There is a slight catch to child watchers, however: you usually start them
359I<after> the child process was created, and this means the process could 420I<after> the child process was created, and this means the process could
360have exited already (and no SIGCHLD will be sent anymore). 421have exited already (and no SIGCHLD will be sent anymore).
361 422
362Not all event models handle this correctly (POE doesn't), but even for 423Not all event models handle this correctly (neither POE nor IO::Async do,
424see their AnyEvent::Impl manpages for details), but even for event models
363event models that I<do> handle this correctly, they usually need to be 425that I<do> handle this correctly, they usually need to be loaded before
364loaded before the process exits (i.e. before you fork in the first place). 426the process exits (i.e. before you fork in the first place). AnyEvent's
427pure perl event loop handles all cases correctly regardless of when you
428start the watcher.
365 429
366This means you cannot create a child watcher as the very first thing in an 430This means you cannot create a child watcher as the very first
367AnyEvent program, you I<have> to create at least one watcher before you 431thing in an AnyEvent program, you I<have> to create at least one
368C<fork> the child (alternatively, you can call C<AnyEvent::detect>). 432watcher before you C<fork> the child (alternatively, you can call
433C<AnyEvent::detect>).
434
435As most event loops do not support waiting for child events, they will be
436emulated by AnyEvent in most cases, in which the latency and race problems
437mentioned in the description of signal watchers apply.
369 438
370Example: fork a process and wait for it 439Example: fork a process and wait for it
371 440
372 my $done = AnyEvent->condvar; 441 my $done = AnyEvent->condvar;
373 442
383 ); 452 );
384 453
385 # do something else, then wait for process exit 454 # do something else, then wait for process exit
386 $done->recv; 455 $done->recv;
387 456
457=head2 IDLE WATCHERS
458
459Sometimes there is a need to do something, but it is not so important
460to do it instantly, but only when there is nothing better to do. This
461"nothing better to do" is usually defined to be "no other events need
462attention by the event loop".
463
464Idle watchers ideally get invoked when the event loop has nothing
465better to do, just before it would block the process to wait for new
466events. Instead of blocking, the idle watcher is invoked.
467
468Most event loops unfortunately do not really support idle watchers (only
469EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
470will simply call the callback "from time to time".
471
472Example: read lines from STDIN, but only process them when the
473program is otherwise idle:
474
475 my @lines; # read data
476 my $idle_w;
477 my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
478 push @lines, scalar <STDIN>;
479
480 # start an idle watcher, if not already done
481 $idle_w ||= AnyEvent->idle (cb => sub {
482 # handle only one line, when there are lines left
483 if (my $line = shift @lines) {
484 print "handled when idle: $line";
485 } else {
486 # otherwise disable the idle watcher again
487 undef $idle_w;
488 }
489 });
490 });
491
388=head2 CONDITION VARIABLES 492=head2 CONDITION VARIABLES
389 493
390If you are familiar with some event loops you will know that all of them 494If you are familiar with some event loops you will know that all of them
391require you to run some blocking "loop", "run" or similar function that 495require you to run some blocking "loop", "run" or similar function that
392will actively watch for new events and call your callbacks. 496will actively watch for new events and call your callbacks.
393 497
394AnyEvent is different, it expects somebody else to run the event loop and 498AnyEvent is slightly different: it expects somebody else to run the event
395will only block when necessary (usually when told by the user). 499loop and will only block when necessary (usually when told by the user).
396 500
397The instrument to do that is called a "condition variable", so called 501The instrument to do that is called a "condition variable", so called
398because they represent a condition that must become true. 502because they represent a condition that must become true.
399 503
504Now is probably a good time to look at the examples further below.
505
400Condition variables can be created by calling the C<< AnyEvent->condvar 506Condition variables can be created by calling the C<< AnyEvent->condvar
401>> method, usually without arguments. The only argument pair allowed is 507>> method, usually without arguments. The only argument pair allowed is
402
403C<cb>, which specifies a callback to be called when the condition variable 508C<cb>, which specifies a callback to be called when the condition variable
404becomes true, with the condition variable as the first argument (but not 509becomes true, with the condition variable as the first argument (but not
405the results). 510the results).
406 511
407After creation, the condition variable is "false" until it becomes "true" 512After creation, the condition variable is "false" until it becomes "true"
412Condition variables are similar to callbacks, except that you can 517Condition variables are similar to callbacks, except that you can
413optionally wait for them. They can also be called merge points - points 518optionally wait for them. They can also be called merge points - points
414in time where multiple outstanding events have been processed. And yet 519in time where multiple outstanding events have been processed. And yet
415another way to call them is transactions - each condition variable can be 520another way to call them is transactions - each condition variable can be
416used to represent a transaction, which finishes at some point and delivers 521used to represent a transaction, which finishes at some point and delivers
417a result. 522a result. And yet some people know them as "futures" - a promise to
523compute/deliver something that you can wait for.
418 524
419Condition variables are very useful to signal that something has finished, 525Condition variables are very useful to signal that something has finished,
420for example, if you write a module that does asynchronous http requests, 526for example, if you write a module that does asynchronous http requests,
421then a condition variable would be the ideal candidate to signal the 527then a condition variable would be the ideal candidate to signal the
422availability of results. The user can either act when the callback is 528availability of results. The user can either act when the callback is
456 after => 1, 562 after => 1,
457 cb => sub { $result_ready->send }, 563 cb => sub { $result_ready->send },
458 ); 564 );
459 565
460 # this "blocks" (while handling events) till the callback 566 # this "blocks" (while handling events) till the callback
461 # calls send 567 # calls -<send
462 $result_ready->recv; 568 $result_ready->recv;
463 569
464Example: wait for a timer, but take advantage of the fact that 570Example: wait for a timer, but take advantage of the fact that condition
465condition variables are also code references. 571variables are also callable directly.
466 572
467 my $done = AnyEvent->condvar; 573 my $done = AnyEvent->condvar;
468 my $delay = AnyEvent->timer (after => 5, cb => $done); 574 my $delay = AnyEvent->timer (after => 5, cb => $done);
469 $done->recv; 575 $done->recv;
470 576
476 582
477 ... 583 ...
478 584
479 my @info = $couchdb->info->recv; 585 my @info = $couchdb->info->recv;
480 586
481And this is how you would just ste a callback to be called whenever the 587And this is how you would just set a callback to be called whenever the
482results are available: 588results are available:
483 589
484 $couchdb->info->cb (sub { 590 $couchdb->info->cb (sub {
485 my @info = $_[0]->recv; 591 my @info = $_[0]->recv;
486 }); 592 });
504immediately from within send. 610immediately from within send.
505 611
506Any arguments passed to the C<send> call will be returned by all 612Any arguments passed to the C<send> call will be returned by all
507future C<< ->recv >> calls. 613future C<< ->recv >> calls.
508 614
509Condition variables are overloaded so one can call them directly 615Condition variables are overloaded so one can call them directly (as if
510(as a code reference). Calling them directly is the same as calling 616they were a code reference). Calling them directly is the same as calling
511C<send>. Note, however, that many C-based event loops do not handle 617C<send>.
512overloading, so as tempting as it may be, passing a condition variable
513instead of a callback does not work. Both the pure perl and EV loops
514support overloading, however, as well as all functions that use perl to
515invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
516example).
517 618
518=item $cv->croak ($error) 619=item $cv->croak ($error)
519 620
520Similar to send, but causes all call's to C<< ->recv >> to invoke 621Similar to send, but causes all call's to C<< ->recv >> to invoke
521C<Carp::croak> with the given error message/object/scalar. 622C<Carp::croak> with the given error message/object/scalar.
522 623
523This can be used to signal any errors to the condition variable 624This can be used to signal any errors to the condition variable
524user/consumer. 625user/consumer. Doing it this way instead of calling C<croak> directly
626delays the error detetcion, but has the overwhelmign advantage that it
627diagnoses the error at the place where the result is expected, and not
628deep in some event clalback without connection to the actual code causing
629the problem.
525 630
526=item $cv->begin ([group callback]) 631=item $cv->begin ([group callback])
527 632
528=item $cv->end 633=item $cv->end
529
530These two methods are EXPERIMENTAL and MIGHT CHANGE.
531 634
532These two methods can be used to combine many transactions/events into 635These two methods can be used to combine many transactions/events into
533one. For example, a function that pings many hosts in parallel might want 636one. For example, a function that pings many hosts in parallel might want
534to use a condition variable for the whole process. 637to use a condition variable for the whole process.
535 638
537C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end 640C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
538>>, the (last) callback passed to C<begin> will be executed. That callback 641>>, the (last) callback passed to C<begin> will be executed. That callback
539is I<supposed> to call C<< ->send >>, but that is not required. If no 642is I<supposed> to call C<< ->send >>, but that is not required. If no
540callback was set, C<send> will be called without any arguments. 643callback was set, C<send> will be called without any arguments.
541 644
542Let's clarify this with the ping example: 645You can think of C<< $cv->send >> giving you an OR condition (one call
646sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
647condition (all C<begin> calls must be C<end>'ed before the condvar sends).
648
649Let's start with a simple example: you have two I/O watchers (for example,
650STDOUT and STDERR for a program), and you want to wait for both streams to
651close before activating a condvar:
652
653 my $cv = AnyEvent->condvar;
654
655 $cv->begin; # first watcher
656 my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
657 defined sysread $fh1, my $buf, 4096
658 or $cv->end;
659 });
660
661 $cv->begin; # second watcher
662 my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
663 defined sysread $fh2, my $buf, 4096
664 or $cv->end;
665 });
666
667 $cv->recv;
668
669This works because for every event source (EOF on file handle), there is
670one call to C<begin>, so the condvar waits for all calls to C<end> before
671sending.
672
673The ping example mentioned above is slightly more complicated, as the
674there are results to be passwd back, and the number of tasks that are
675begung can potentially be zero:
543 676
544 my $cv = AnyEvent->condvar; 677 my $cv = AnyEvent->condvar;
545 678
546 my %result; 679 my %result;
547 $cv->begin (sub { $cv->send (\%result) }); 680 $cv->begin (sub { $cv->send (\%result) });
567loop, which serves two important purposes: first, it sets the callback 700loop, which serves two important purposes: first, it sets the callback
568to be called once the counter reaches C<0>, and second, it ensures that 701to be called once the counter reaches C<0>, and second, it ensures that
569C<send> is called even when C<no> hosts are being pinged (the loop 702C<send> is called even when C<no> hosts are being pinged (the loop
570doesn't execute once). 703doesn't execute once).
571 704
572This is the general pattern when you "fan out" into multiple subrequests: 705This is the general pattern when you "fan out" into multiple (but
573use an outer C<begin>/C<end> pair to set the callback and ensure C<end> 706potentially none) subrequests: use an outer C<begin>/C<end> pair to set
574is called at least once, and then, for each subrequest you start, call 707the callback and ensure C<end> is called at least once, and then, for each
575C<begin> and for each subrequest you finish, call C<end>. 708subrequest you start, call C<begin> and for each subrequest you finish,
709call C<end>.
576 710
577=back 711=back
578 712
579=head3 METHODS FOR CONSUMERS 713=head3 METHODS FOR CONSUMERS
580 714
596function will call C<croak>. 730function will call C<croak>.
597 731
598In list context, all parameters passed to C<send> will be returned, 732In list context, all parameters passed to C<send> will be returned,
599in scalar context only the first one will be returned. 733in scalar context only the first one will be returned.
600 734
735Note that doing a blocking wait in a callback is not supported by any
736event loop, that is, recursive invocation of a blocking C<< ->recv
737>> is not allowed, and the C<recv> call will C<croak> if such a
738condition is detected. This condition can be slightly loosened by using
739L<Coro::AnyEvent>, which allows you to do a blocking C<< ->recv >> from
740any thread that doesn't run the event loop itself.
741
601Not all event models support a blocking wait - some die in that case 742Not all event models support a blocking wait - some die in that case
602(programs might want to do that to stay interactive), so I<if you are 743(programs might want to do that to stay interactive), so I<if you are
603using this from a module, never require a blocking wait>, but let the 744using this from a module, never require a blocking wait>. Instead, let the
604caller decide whether the call will block or not (for example, by coupling 745caller decide whether the call will block or not (for example, by coupling
605condition variables with some kind of request results and supporting 746condition variables with some kind of request results and supporting
606callbacks so the caller knows that getting the result will not block, 747callbacks so the caller knows that getting the result will not block,
607while still supporting blocking waits if the caller so desires). 748while still supporting blocking waits if the caller so desires).
608 749
609Another reason I<never> to C<< ->recv >> in a module is that you cannot
610sensibly have two C<< ->recv >>'s in parallel, as that would require
611multiple interpreters or coroutines/threads, none of which C<AnyEvent>
612can supply.
613
614The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
615fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
616versions and also integrates coroutines into AnyEvent, making blocking
617C<< ->recv >> calls perfectly safe as long as they are done from another
618coroutine (one that doesn't run the event loop).
619
620You can ensure that C<< -recv >> never blocks by setting a callback and 750You can ensure that C<< -recv >> never blocks by setting a callback and
621only calling C<< ->recv >> from within that callback (or at a later 751only calling C<< ->recv >> from within that callback (or at a later
622time). This will work even when the event loop does not support blocking 752time). This will work even when the event loop does not support blocking
623waits otherwise. 753waits otherwise.
624 754
637variable itself. Calling C<recv> inside the callback or at any later time 767variable itself. Calling C<recv> inside the callback or at any later time
638is guaranteed not to block. 768is guaranteed not to block.
639 769
640=back 770=back
641 771
772=head1 SUPPORTED EVENT LOOPS/BACKENDS
773
774The available backend classes are (every class has its own manpage):
775
776=over 4
777
778=item Backends that are autoprobed when no other event loop can be found.
779
780EV is the preferred backend when no other event loop seems to be in
781use. If EV is not installed, then AnyEvent will try Event, and, failing
782that, will fall back to its own pure-perl implementation, which is
783available everywhere as it comes with AnyEvent itself.
784
785 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
786 AnyEvent::Impl::Event based on Event, very stable, few glitches.
787 AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
788
789=item Backends that are transparently being picked up when they are used.
790
791These will be used when they are currently loaded when the first watcher
792is created, in which case it is assumed that the application is using
793them. This means that AnyEvent will automatically pick the right backend
794when the main program loads an event module before anything starts to
795create watchers. Nothing special needs to be done by the main program.
796
797 AnyEvent::Impl::Glib based on Glib, slow but very stable.
798 AnyEvent::Impl::Tk based on Tk, very broken.
799 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
800 AnyEvent::Impl::POE based on POE, very slow, some limitations.
801
802=item Backends with special needs.
803
804Qt requires the Qt::Application to be instantiated first, but will
805otherwise be picked up automatically. As long as the main program
806instantiates the application before any AnyEvent watchers are created,
807everything should just work.
808
809 AnyEvent::Impl::Qt based on Qt.
810
811Support for IO::Async can only be partial, as it is too broken and
812architecturally limited to even support the AnyEvent API. It also
813is the only event loop that needs the loop to be set explicitly, so
814it can only be used by a main program knowing about AnyEvent. See
815L<AnyEvent::Impl::Async> for the gory details.
816
817 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
818
819=item Event loops that are indirectly supported via other backends.
820
821Some event loops can be supported via other modules:
822
823There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
824
825B<WxWidgets> has no support for watching file handles. However, you can
826use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
827polls 20 times per second, which was considered to be too horrible to even
828consider for AnyEvent.
829
830B<Prima> is not supported as nobody seems to be using it, but it has a POE
831backend, so it can be supported through POE.
832
833AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
834load L<POE> when detecting them, in the hope that POE will pick them up,
835in which case everything will be automatic.
836
837=back
838
642=head1 GLOBAL VARIABLES AND FUNCTIONS 839=head1 GLOBAL VARIABLES AND FUNCTIONS
643 840
841These are not normally required to use AnyEvent, but can be useful to
842write AnyEvent extension modules.
843
644=over 4 844=over 4
645 845
646=item $AnyEvent::MODEL 846=item $AnyEvent::MODEL
647 847
648Contains C<undef> until the first watcher is being created. Then it 848Contains C<undef> until the first watcher is being created, before the
849backend has been autodetected.
850
649contains the event model that is being used, which is the name of the 851Afterwards it contains the event model that is being used, which is the
650Perl class implementing the model. This class is usually one of the 852name of the Perl class implementing the model. This class is usually one
651C<AnyEvent::Impl:xxx> modules, but can be any other class in the case 853of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the
652AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). 854case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
653 855will be C<urxvt::anyevent>).
654The known classes so far are:
655
656 AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
657 AnyEvent::Impl::Event based on Event, second best choice.
658 AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
659 AnyEvent::Impl::Glib based on Glib, third-best choice.
660 AnyEvent::Impl::Tk based on Tk, very bad choice.
661 AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
662 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
663 AnyEvent::Impl::POE based on POE, not generic enough for full support.
664
665There is no support for WxWidgets, as WxWidgets has no support for
666watching file handles. However, you can use WxWidgets through the
667POE Adaptor, as POE has a Wx backend that simply polls 20 times per
668second, which was considered to be too horrible to even consider for
669AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
670it's adaptor.
671
672AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
673autodetecting them.
674 856
675=item AnyEvent::detect 857=item AnyEvent::detect
676 858
677Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 859Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
678if necessary. You should only call this function right before you would 860if necessary. You should only call this function right before you would
679have created an AnyEvent watcher anyway, that is, as late as possible at 861have created an AnyEvent watcher anyway, that is, as late as possible at
680runtime. 862runtime, and not e.g. while initialising of your module.
863
864If you need to do some initialisation before AnyEvent watchers are
865created, use C<post_detect>.
681 866
682=item $guard = AnyEvent::post_detect { BLOCK } 867=item $guard = AnyEvent::post_detect { BLOCK }
683 868
684Arranges for the code block to be executed as soon as the event model is 869Arranges for the code block to be executed as soon as the event model is
685autodetected (or immediately if this has already happened). 870autodetected (or immediately if this has already happened).
686 871
872The block will be executed I<after> the actual backend has been detected
873(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
874created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
875other initialisations - see the sources of L<AnyEvent::Strict> or
876L<AnyEvent::AIO> to see how this is used.
877
878The most common usage is to create some global watchers, without forcing
879event module detection too early, for example, L<AnyEvent::AIO> creates
880and installs the global L<IO::AIO> watcher in a C<post_detect> block to
881avoid autodetecting the event module at load time.
882
687If called in scalar or list context, then it creates and returns an object 883If called in scalar or list context, then it creates and returns an object
688that automatically removes the callback again when it is destroyed. See 884that automatically removes the callback again when it is destroyed (or
885C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
689L<Coro::BDB> for a case where this is useful. 886a case where this is useful.
887
888Example: Create a watcher for the IO::AIO module and store it in
889C<$WATCHER>. Only do so after the event loop is initialised, though.
890
891 our WATCHER;
892
893 my $guard = AnyEvent::post_detect {
894 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
895 };
896
897 # the ||= is important in case post_detect immediately runs the block,
898 # as to not clobber the newly-created watcher. assigning both watcher and
899 # post_detect guard to the same variable has the advantage of users being
900 # able to just C<undef $WATCHER> if the watcher causes them grief.
901
902 $WATCHER ||= $guard;
690 903
691=item @AnyEvent::post_detect 904=item @AnyEvent::post_detect
692 905
693If there are any code references in this array (you can C<push> to it 906If there are any code references in this array (you can C<push> to it
694before or after loading AnyEvent), then they will called directly after 907before or after loading AnyEvent), then they will called directly after
695the event loop has been chosen. 908the event loop has been chosen.
696 909
697You should check C<$AnyEvent::MODEL> before adding to this array, though: 910You should check C<$AnyEvent::MODEL> before adding to this array, though:
698if it contains a true value then the event loop has already been detected, 911if it is defined then the event loop has already been detected, and the
699and the array will be ignored. 912array will be ignored.
700 913
701Best use C<AnyEvent::post_detect { BLOCK }> instead. 914Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
915it,as it takes care of these details.
916
917This variable is mainly useful for modules that can do something useful
918when AnyEvent is used and thus want to know when it is initialised, but do
919not need to even load it by default. This array provides the means to hook
920into AnyEvent passively, without loading it.
702 921
703=back 922=back
704 923
705=head1 WHAT TO DO IN A MODULE 924=head1 WHAT TO DO IN A MODULE
706 925
761 980
762 981
763=head1 OTHER MODULES 982=head1 OTHER MODULES
764 983
765The following is a non-exhaustive list of additional modules that use 984The following is a non-exhaustive list of additional modules that use
766AnyEvent and can therefore be mixed easily with other AnyEvent modules 985AnyEvent as a client and can therefore be mixed easily with other AnyEvent
767in the same program. Some of the modules come with AnyEvent, some are 986modules and other event loops in the same program. Some of the modules
768available via CPAN. 987come with AnyEvent, most are available via CPAN.
769 988
770=over 4 989=over 4
771 990
772=item L<AnyEvent::Util> 991=item L<AnyEvent::Util>
773 992
782 1001
783=item L<AnyEvent::Handle> 1002=item L<AnyEvent::Handle>
784 1003
785Provide read and write buffers, manages watchers for reads and writes, 1004Provide read and write buffers, manages watchers for reads and writes,
786supports raw and formatted I/O, I/O queued and fully transparent and 1005supports raw and formatted I/O, I/O queued and fully transparent and
787non-blocking SSL/TLS. 1006non-blocking SSL/TLS (via L<AnyEvent::TLS>.
788 1007
789=item L<AnyEvent::DNS> 1008=item L<AnyEvent::DNS>
790 1009
791Provides rich asynchronous DNS resolver capabilities. 1010Provides rich asynchronous DNS resolver capabilities.
792 1011
820 1039
821=item L<AnyEvent::GPSD> 1040=item L<AnyEvent::GPSD>
822 1041
823A non-blocking interface to gpsd, a daemon delivering GPS information. 1042A non-blocking interface to gpsd, a daemon delivering GPS information.
824 1043
1044=item L<AnyEvent::IRC>
1045
1046AnyEvent based IRC client module family (replacing the older Net::IRC3).
1047
1048=item L<AnyEvent::XMPP>
1049
1050AnyEvent based XMPP (Jabber protocol) module family (replacing the older
1051Net::XMPP2>.
1052
825=item L<AnyEvent::IGS> 1053=item L<AnyEvent::IGS>
826 1054
827A non-blocking interface to the Internet Go Server protocol (used by 1055A non-blocking interface to the Internet Go Server protocol (used by
828L<App::IGS>). 1056L<App::IGS>).
829 1057
830=item L<AnyEvent::IRC>
831
832AnyEvent based IRC client module family (replacing the older Net::IRC3).
833
834=item L<Net::XMPP2>
835
836AnyEvent based XMPP (Jabber protocol) module family.
837
838=item L<Net::FCP> 1058=item L<Net::FCP>
839 1059
840AnyEvent-based implementation of the Freenet Client Protocol, birthplace 1060AnyEvent-based implementation of the Freenet Client Protocol, birthplace
841of AnyEvent. 1061of AnyEvent.
842 1062
846 1066
847=item L<Coro> 1067=item L<Coro>
848 1068
849Has special support for AnyEvent via L<Coro::AnyEvent>. 1069Has special support for AnyEvent via L<Coro::AnyEvent>.
850 1070
851=item L<IO::Lambda>
852
853The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
854
855=back 1071=back
856 1072
857=cut 1073=cut
858 1074
859package AnyEvent; 1075package AnyEvent;
860 1076
1077# basically a tuned-down version of common::sense
1078sub common_sense {
861no warnings; 1079 # no warnings
1080 ${^WARNING_BITS} ^= ${^WARNING_BITS};
862use strict qw(vars subs); 1081 # use strict vars subs
1082 $^H |= 0x00000600;
1083}
863 1084
1085BEGIN { AnyEvent::common_sense }
1086
864use Carp; 1087use Carp ();
865 1088
866our $VERSION = 4.32; 1089our $VERSION = 4.86;
867our $MODEL; 1090our $MODEL;
868 1091
869our $AUTOLOAD; 1092our $AUTOLOAD;
870our @ISA; 1093our @ISA;
871 1094
872our @REGISTRY; 1095our @REGISTRY;
873 1096
874our $WIN32; 1097our $WIN32;
875 1098
1099our $VERBOSE;
1100
876BEGIN { 1101BEGIN {
877 my $win32 = ! ! ($^O =~ /mswin32/i); 1102 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
878 eval "sub WIN32(){ $win32 }"; 1103 eval "sub TAINT(){ " . (${^TAINT}*1) . " }";
879}
880 1104
1105 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
1106 if ${^TAINT};
1107
881our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 1108 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
1109
1110}
1111
1112our $MAX_SIGNAL_LATENCY = 10;
882 1113
883our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred 1114our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
884 1115
885{ 1116{
886 my $idx; 1117 my $idx;
894 [Event:: => AnyEvent::Impl::Event::], 1125 [Event:: => AnyEvent::Impl::Event::],
895 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 1126 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
896 # everything below here will not be autoprobed 1127 # everything below here will not be autoprobed
897 # as the pureperl backend should work everywhere 1128 # as the pureperl backend should work everywhere
898 # and is usually faster 1129 # and is usually faster
899 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
900 [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers 1130 [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
901 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy 1131 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
1132 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
902 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program 1133 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program
903 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 1134 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
904 [Wx:: => AnyEvent::Impl::POE::], 1135 [Wx:: => AnyEvent::Impl::POE::],
905 [Prima:: => AnyEvent::Impl::POE::], 1136 [Prima:: => AnyEvent::Impl::POE::],
1137 # IO::Async is just too broken - we would need workarounds for its
1138 # byzantine signal and broken child handling, among others.
1139 # IO::Async is rather hard to detect, as it doesn't have any
1140 # obvious default class.
1141# [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
1142# [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
1143# [IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
906); 1144);
907 1145
908our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); 1146our %method = map +($_ => 1),
1147 qw(io timer time now now_update signal child idle condvar one_event DESTROY);
909 1148
910our @post_detect; 1149our @post_detect;
911 1150
912sub post_detect(&) { 1151sub post_detect(&) {
913 my ($cb) = @_; 1152 my ($cb) = @_;
914 1153
915 if ($MODEL) { 1154 if ($MODEL) {
916 $cb->(); 1155 $cb->();
917 1156
918 1 1157 undef
919 } else { 1158 } else {
920 push @post_detect, $cb; 1159 push @post_detect, $cb;
921 1160
922 defined wantarray 1161 defined wantarray
923 ? bless \$cb, "AnyEvent::Util::PostDetect" 1162 ? bless \$cb, "AnyEvent::Util::postdetect"
924 : () 1163 : ()
925 } 1164 }
926} 1165}
927 1166
928sub AnyEvent::Util::PostDetect::DESTROY { 1167sub AnyEvent::Util::postdetect::DESTROY {
929 @post_detect = grep $_ != ${$_[0]}, @post_detect; 1168 @post_detect = grep $_ != ${$_[0]}, @post_detect;
930} 1169}
931 1170
932sub detect() { 1171sub detect() {
933 unless ($MODEL) { 1172 unless ($MODEL) {
934 no strict 'refs';
935 local $SIG{__DIE__}; 1173 local $SIG{__DIE__};
936 1174
937 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 1175 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
938 my $model = "AnyEvent::Impl::$1"; 1176 my $model = "AnyEvent::Impl::$1";
939 if (eval "require $model") { 1177 if (eval "require $model") {
940 $MODEL = $model; 1178 $MODEL = $model;
941 warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1; 1179 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
942 } else { 1180 } else {
943 warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose; 1181 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
944 } 1182 }
945 } 1183 }
946 1184
947 # check for already loaded models 1185 # check for already loaded models
948 unless ($MODEL) { 1186 unless ($MODEL) {
949 for (@REGISTRY, @models) { 1187 for (@REGISTRY, @models) {
950 my ($package, $model) = @$_; 1188 my ($package, $model) = @$_;
951 if (${"$package\::VERSION"} > 0) { 1189 if (${"$package\::VERSION"} > 0) {
952 if (eval "require $model") { 1190 if (eval "require $model") {
953 $MODEL = $model; 1191 $MODEL = $model;
954 warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1; 1192 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
955 last; 1193 last;
956 } 1194 }
957 } 1195 }
958 } 1196 }
959 1197
964 my ($package, $model) = @$_; 1202 my ($package, $model) = @$_;
965 if (eval "require $package" 1203 if (eval "require $package"
966 and ${"$package\::VERSION"} > 0 1204 and ${"$package\::VERSION"} > 0
967 and eval "require $model") { 1205 and eval "require $model") {
968 $MODEL = $model; 1206 $MODEL = $model;
969 warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1; 1207 warn "AnyEvent: autoprobed model '$model', using it.\n" if $VERBOSE >= 2;
970 last; 1208 last;
971 } 1209 }
972 } 1210 }
973 1211
974 $MODEL 1212 $MODEL
975 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib."; 1213 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n";
976 } 1214 }
977 } 1215 }
978 1216
979 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 1217 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
980 1218
990 1228
991sub AUTOLOAD { 1229sub AUTOLOAD {
992 (my $func = $AUTOLOAD) =~ s/.*://; 1230 (my $func = $AUTOLOAD) =~ s/.*://;
993 1231
994 $method{$func} 1232 $method{$func}
995 or croak "$func: not a valid method for AnyEvent objects"; 1233 or Carp::croak "$func: not a valid method for AnyEvent objects";
996 1234
997 detect unless $MODEL; 1235 detect unless $MODEL;
998 1236
999 my $class = shift; 1237 my $class = shift;
1000 $class->$func (@_); 1238 $class->$func (@_);
1001} 1239}
1002 1240
1003# utility function to dup a filehandle. this is used by many backends 1241# utility function to dup a filehandle. this is used by many backends
1004# to support binding more than one watcher per filehandle (they usually 1242# to support binding more than one watcher per filehandle (they usually
1005# allow only one watcher per fd, so we dup it to get a different one). 1243# allow only one watcher per fd, so we dup it to get a different one).
1006sub _dupfh($$$$) { 1244sub _dupfh($$;$$) {
1007 my ($poll, $fh, $r, $w) = @_; 1245 my ($poll, $fh, $r, $w) = @_;
1008 1246
1009 require Fcntl;
1010
1011 # cygwin requires the fh mode to be matching, unix doesn't 1247 # cygwin requires the fh mode to be matching, unix doesn't
1012 my ($rw, $mode) = $poll eq "r" ? ($r, "<") 1248 my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
1013 : $poll eq "w" ? ($w, ">")
1014 : Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1015 1249
1016 open my $fh2, "$mode&" . fileno $fh 1250 open my $fh2, $mode, $fh
1017 or die "cannot dup() filehandle: $!"; 1251 or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
1018 1252
1019 # we assume CLOEXEC is already set by perl in all important cases 1253 # we assume CLOEXEC is already set by perl in all important cases
1020 1254
1021 ($fh2, $rw) 1255 ($fh2, $rw)
1022} 1256}
1023 1257
1024package AnyEvent::Base; 1258package AnyEvent::Base;
1025 1259
1026# default implementation for now and time 1260# default implementations for many methods
1027 1261
1028BEGIN { 1262sub _time {
1263 # probe for availability of Time::HiRes
1029 if (eval "use Time::HiRes (); time (); 1") { 1264 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
1265 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
1030 *_time = \&Time::HiRes::time; 1266 *_time = \&Time::HiRes::time;
1031 # if (eval "use POSIX (); (POSIX::times())... 1267 # if (eval "use POSIX (); (POSIX::times())...
1032 } else { 1268 } else {
1269 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
1033 *_time = sub { time }; # epic fail 1270 *_time = sub { time }; # epic fail
1034 } 1271 }
1272
1273 &_time
1035} 1274}
1036 1275
1037sub time { _time } 1276sub time { _time }
1038sub now { _time } 1277sub now { _time }
1278sub now_update { }
1039 1279
1040# default implementation for ->condvar 1280# default implementation for ->condvar
1041 1281
1042sub condvar { 1282sub condvar {
1043 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: 1283 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1044} 1284}
1045 1285
1046# default implementation for ->signal 1286# default implementation for ->signal
1047 1287
1048our %SIG_CB; 1288our $HAVE_ASYNC_INTERRUPT;
1289our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
1290our (%SIG_ASY, %SIG_ASY_W);
1291our ($SIG_COUNT, $SIG_TW);
1049 1292
1293sub _signal_exec {
1294 $HAVE_ASYNC_INTERRUPT
1295 ? $SIGPIPE_R->drain
1296 : sysread $SIGPIPE_R, my $dummy, 9;
1297
1298 while (%SIG_EV) {
1299 for (keys %SIG_EV) {
1300 delete $SIG_EV{$_};
1301 $_->() for values %{ $SIG_CB{$_} || {} };
1302 }
1303 }
1304}
1305
1306# install a dumym wakeupw atcher to reduce signal catching latency
1307sub _sig_add() {
1308 unless ($SIG_COUNT++) {
1309 # try to align timer on a full-second boundary, if possible
1310 my $NOW = AnyEvent->now;
1311
1312 $SIG_TW = AnyEvent->timer (
1313 after => $MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
1314 interval => $MAX_SIGNAL_LATENCY,
1315 cb => sub { }, # just for the PERL_ASYNC_CHECK
1316 );
1317 }
1318}
1319
1320sub _sig_del {
1321 undef $SIG_TW
1322 unless --$SIG_COUNT;
1323}
1324
1050sub signal { 1325sub _signal {
1051 my (undef, %arg) = @_; 1326 my (undef, %arg) = @_;
1052 1327
1053 my $signal = uc $arg{signal} 1328 my $signal = uc $arg{signal}
1054 or Carp::croak "required option 'signal' is missing"; 1329 or Carp::croak "required option 'signal' is missing";
1055 1330
1056 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1331 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1332
1333 if ($HAVE_ASYNC_INTERRUPT) {
1334 # async::interrupt
1335
1336 $SIG_ASY{$signal} ||= do {
1337 my $asy = new Async::Interrupt
1338 cb => sub { undef $SIG_EV{$signal} },
1339 signal => $signal,
1340 pipe => [$SIGPIPE_R->filenos],
1341 ;
1342 $asy->pipe_autodrain (0);
1343
1344 $asy
1345 };
1346
1347 } else {
1348 # pure perl
1349
1057 $SIG{$signal} ||= sub { 1350 $SIG{$signal} ||= sub {
1058 $_->() for values %{ $SIG_CB{$signal} || {} }; 1351 local $!;
1352 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
1353 undef $SIG_EV{$signal};
1354 };
1355
1356 # can't do signal processing without introducing races in pure perl,
1357 # so limit the signal latency.
1358 _sig_add;
1059 }; 1359 }
1060 1360
1061 bless [$signal, $arg{cb}], "AnyEvent::Base::Signal" 1361 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1062} 1362}
1063 1363
1364sub signal {
1365 # probe for availability of Async::Interrupt
1366 if (!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT} && eval "use Async::Interrupt 0.6 (); 1") {
1367 warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
1368
1369 $HAVE_ASYNC_INTERRUPT = 1;
1370 $SIGPIPE_R = new Async::Interrupt::EventPipe;
1371 $SIG_IO = AnyEvent->io (fh => $SIGPIPE_R->fileno, poll => "r", cb => \&_signal_exec);
1372
1373 } else {
1374 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
1375
1376 require Fcntl;
1377
1378 if (AnyEvent::WIN32) {
1379 require AnyEvent::Util;
1380
1381 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1382 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R) if $SIGPIPE_R;
1383 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W) if $SIGPIPE_W; # just in case
1384 } else {
1385 pipe $SIGPIPE_R, $SIGPIPE_W;
1386 fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;
1387 fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case
1388
1389 # not strictly required, as $^F is normally 2, but let's make sure...
1390 fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
1391 fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
1392 }
1393
1394 $SIGPIPE_R
1395 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
1396
1397 $SIG_IO = AnyEvent->io (fh => $SIGPIPE_R, poll => "r", cb => \&_signal_exec);
1398 }
1399
1400 *signal = \&_signal;
1401 &signal
1402}
1403
1064sub AnyEvent::Base::Signal::DESTROY { 1404sub AnyEvent::Base::signal::DESTROY {
1065 my ($signal, $cb) = @{$_[0]}; 1405 my ($signal, $cb) = @{$_[0]};
1066 1406
1407 _sig_del;
1408
1067 delete $SIG_CB{$signal}{$cb}; 1409 delete $SIG_CB{$signal}{$cb};
1068 1410
1411 $HAVE_ASYNC_INTERRUPT
1412 ? delete $SIG_ASY{$signal}
1413 : # delete doesn't work with older perls - they then
1414 # print weird messages, or just unconditionally exit
1415 # instead of getting the default action.
1416 undef $SIG{$signal}
1069 delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} }; 1417 unless keys %{ $SIG_CB{$signal} };
1070} 1418}
1071 1419
1072# default implementation for ->child 1420# default implementation for ->child
1073 1421
1074our %PID_CB; 1422our %PID_CB;
1075our $CHLD_W; 1423our $CHLD_W;
1076our $CHLD_DELAY_W; 1424our $CHLD_DELAY_W;
1077our $PID_IDLE;
1078our $WNOHANG; 1425our $WNOHANG;
1079 1426
1080sub _child_wait { 1427sub _sigchld {
1081 while (0 < (my $pid = waitpid -1, $WNOHANG)) { 1428 while (0 < (my $pid = waitpid -1, $WNOHANG)) {
1429 $_->($pid, $?)
1082 $_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }), 1430 for values %{ $PID_CB{$pid} || {} },
1083 (values %{ $PID_CB{0} || {} }); 1431 values %{ $PID_CB{0} || {} };
1084 } 1432 }
1085
1086 undef $PID_IDLE;
1087}
1088
1089sub _sigchld {
1090 # make sure we deliver these changes "synchronous" with the event loop.
1091 $CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
1092 undef $CHLD_DELAY_W;
1093 &_child_wait;
1094 });
1095} 1433}
1096 1434
1097sub child { 1435sub child {
1098 my (undef, %arg) = @_; 1436 my (undef, %arg) = @_;
1099 1437
1100 defined (my $pid = $arg{pid} + 0) 1438 defined (my $pid = $arg{pid} + 0)
1101 or Carp::croak "required option 'pid' is missing"; 1439 or Carp::croak "required option 'pid' is missing";
1102 1440
1103 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 1441 $PID_CB{$pid}{$arg{cb}} = $arg{cb};
1104 1442
1105 unless ($WNOHANG) { 1443 # WNOHANG is almost cetrainly 1 everywhere
1444 $WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
1445 ? 1
1106 $WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1; 1446 : eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1107 }
1108 1447
1109 unless ($CHLD_W) { 1448 unless ($CHLD_W) {
1110 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); 1449 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
1111 # child could be a zombie already, so make at least one round 1450 # child could be a zombie already, so make at least one round
1112 &_sigchld; 1451 &_sigchld;
1113 } 1452 }
1114 1453
1115 bless [$pid, $arg{cb}], "AnyEvent::Base::Child" 1454 bless [$pid, $arg{cb}], "AnyEvent::Base::child"
1116} 1455}
1117 1456
1118sub AnyEvent::Base::Child::DESTROY { 1457sub AnyEvent::Base::child::DESTROY {
1119 my ($pid, $cb) = @{$_[0]}; 1458 my ($pid, $cb) = @{$_[0]};
1120 1459
1121 delete $PID_CB{$pid}{$cb}; 1460 delete $PID_CB{$pid}{$cb};
1122 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 1461 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1123 1462
1124 undef $CHLD_W unless keys %PID_CB; 1463 undef $CHLD_W unless keys %PID_CB;
1125} 1464}
1126 1465
1466# idle emulation is done by simply using a timer, regardless
1467# of whether the process is idle or not, and not letting
1468# the callback use more than 50% of the time.
1469sub idle {
1470 my (undef, %arg) = @_;
1471
1472 my ($cb, $w, $rcb) = $arg{cb};
1473
1474 $rcb = sub {
1475 if ($cb) {
1476 $w = _time;
1477 &$cb;
1478 $w = _time - $w;
1479
1480 # never use more then 50% of the time for the idle watcher,
1481 # within some limits
1482 $w = 0.0001 if $w < 0.0001;
1483 $w = 5 if $w > 5;
1484
1485 $w = AnyEvent->timer (after => $w, cb => $rcb);
1486 } else {
1487 # clean up...
1488 undef $w;
1489 undef $rcb;
1490 }
1491 };
1492
1493 $w = AnyEvent->timer (after => 0.05, cb => $rcb);
1494
1495 bless \\$cb, "AnyEvent::Base::idle"
1496}
1497
1498sub AnyEvent::Base::idle::DESTROY {
1499 undef $${$_[0]};
1500}
1501
1127package AnyEvent::CondVar; 1502package AnyEvent::CondVar;
1128 1503
1129our @ISA = AnyEvent::CondVar::Base::; 1504our @ISA = AnyEvent::CondVar::Base::;
1130 1505
1131package AnyEvent::CondVar::Base; 1506package AnyEvent::CondVar::Base;
1132 1507
1133use overload 1508#use overload
1134 '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, 1509# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1135 fallback => 1; 1510# fallback => 1;
1511
1512# save 300+ kilobytes by dirtily hardcoding overloading
1513${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
1514*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
1515*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
1516${'AnyEvent::CondVar::Base::()'} = 1; # fallback
1517
1518our $WAITING;
1136 1519
1137sub _send { 1520sub _send {
1138 # nop 1521 # nop
1139} 1522}
1140 1523
1153sub ready { 1536sub ready {
1154 $_[0]{_ae_sent} 1537 $_[0]{_ae_sent}
1155} 1538}
1156 1539
1157sub _wait { 1540sub _wait {
1541 $WAITING
1542 and !$_[0]{_ae_sent}
1543 and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
1544
1545 local $WAITING = 1;
1158 AnyEvent->one_event while !$_[0]{_ae_sent}; 1546 AnyEvent->one_event while !$_[0]{_ae_sent};
1159} 1547}
1160 1548
1161sub recv { 1549sub recv {
1162 $_[0]->_wait; 1550 $_[0]->_wait;
1203so on. 1591so on.
1204 1592
1205=head1 ENVIRONMENT VARIABLES 1593=head1 ENVIRONMENT VARIABLES
1206 1594
1207The following environment variables are used by this module or its 1595The following environment variables are used by this module or its
1208submodules: 1596submodules.
1597
1598Note that AnyEvent will remove I<all> environment variables starting with
1599C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
1600enabled.
1209 1601
1210=over 4 1602=over 4
1211 1603
1212=item C<PERL_ANYEVENT_VERBOSE> 1604=item C<PERL_ANYEVENT_VERBOSE>
1213 1605
1220C<PERL_ANYEVENT_MODEL>. 1612C<PERL_ANYEVENT_MODEL>.
1221 1613
1222When set to C<2> or higher, cause AnyEvent to report to STDERR which event 1614When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1223model it chooses. 1615model it chooses.
1224 1616
1617When set to C<8> or higher, then AnyEvent will report extra information on
1618which optional modules it loads and how it implements certain features.
1619
1225=item C<PERL_ANYEVENT_STRICT> 1620=item C<PERL_ANYEVENT_STRICT>
1226 1621
1227AnyEvent does not do much argument checking by default, as thorough 1622AnyEvent does not do much argument checking by default, as thorough
1228argument checking is very costly. Setting this variable to a true value 1623argument checking is very costly. Setting this variable to a true value
1229will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly 1624will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1230check the arguments passed to most method calls. If it finds any problems 1625check the arguments passed to most method calls. If it finds any problems,
1231it will croak. 1626it will croak.
1232 1627
1233In other words, enables "strict" mode. 1628In other words, enables "strict" mode.
1234 1629
1235Unlike C<use strict>, it is definitely recommended ot keep it off in 1630Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense>
1236production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while 1631>>, it is definitely recommended to keep it off in production. Keeping
1237developing programs can be very useful, however. 1632C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
1633can be very useful, however.
1238 1634
1239=item C<PERL_ANYEVENT_MODEL> 1635=item C<PERL_ANYEVENT_MODEL>
1240 1636
1241This can be used to specify the event model to be used by AnyEvent, before 1637This can be used to specify the event model to be used by AnyEvent, before
1242auto detection and -probing kicks in. It must be a string consisting 1638auto detection and -probing kicks in. It must be a string consisting
1263used, and preference will be given to protocols mentioned earlier in the 1659used, and preference will be given to protocols mentioned earlier in the
1264list. 1660list.
1265 1661
1266This variable can effectively be used for denial-of-service attacks 1662This variable can effectively be used for denial-of-service attacks
1267against local programs (e.g. when setuid), although the impact is likely 1663against local programs (e.g. when setuid), although the impact is likely
1268small, as the program has to handle connection errors already- 1664small, as the program has to handle conenction and other failures anyways.
1269 1665
1270Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6, 1666Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1271but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4> 1667but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1272- only support IPv4, never try to resolve or contact IPv6 1668- only support IPv4, never try to resolve or contact IPv6
1273addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or 1669addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1285 1681
1286=item C<PERL_ANYEVENT_MAX_FORKS> 1682=item C<PERL_ANYEVENT_MAX_FORKS>
1287 1683
1288The maximum number of child processes that C<AnyEvent::Util::fork_call> 1684The maximum number of child processes that C<AnyEvent::Util::fork_call>
1289will create in parallel. 1685will create in parallel.
1686
1687=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
1688
1689The default value for the C<max_outstanding> parameter for the default DNS
1690resolver - this is the maximum number of parallel DNS requests that are
1691sent to the DNS server.
1692
1693=item C<PERL_ANYEVENT_RESOLV_CONF>
1694
1695The file to use instead of F</etc/resolv.conf> (or OS-specific
1696configuration) in the default resolver. When set to the empty string, no
1697default config will be used.
1698
1699=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
1700
1701When neither C<ca_file> nor C<ca_path> was specified during
1702L<AnyEvent::TLS> context creation, and either of these environment
1703variables exist, they will be used to specify CA certificate locations
1704instead of a system-dependent default.
1705
1706=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
1707
1708When these are set to C<1>, then the respective modules are not
1709loaded. Mostly good for testing AnyEvent itself.
1290 1710
1291=back 1711=back
1292 1712
1293=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 1713=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1294 1714
1536 1956
1537 name watchers bytes create invoke destroy comment 1957 name watchers bytes create invoke destroy comment
1538 EV/EV 400000 224 0.47 0.35 0.27 EV native interface 1958 EV/EV 400000 224 0.47 0.35 0.27 EV native interface
1539 EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers 1959 EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers
1540 CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal 1960 CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal
1541 Perl/Any 100000 452 4.14 0.75 0.99 pure perl implementation 1961 Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation
1542 Event/Event 16000 517 32.20 31.80 0.81 Event native interface 1962 Event/Event 16000 517 32.20 31.80 0.81 Event native interface
1543 Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers 1963 Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers
1964 IOAsync/Any 16000 989 38.10 32.77 11.13 via IO::Async::Loop::IO_Poll
1965 IOAsync/Any 16000 990 37.59 29.50 10.61 via IO::Async::Loop::Epoll
1544 Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour 1966 Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour
1545 Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers 1967 Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers
1546 POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event 1968 POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event
1547 POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select 1969 POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select
1548 1970
1577performance becomes really bad with lots of file descriptors (and few of 1999performance becomes really bad with lots of file descriptors (and few of
1578them active), of course, but this was not subject of this benchmark. 2000them active), of course, but this was not subject of this benchmark.
1579 2001
1580The C<Event> module has a relatively high setup and callback invocation 2002The C<Event> module has a relatively high setup and callback invocation
1581cost, but overall scores in on the third place. 2003cost, but overall scores in on the third place.
2004
2005C<IO::Async> performs admirably well, about on par with C<Event>, even
2006when using its pure perl backend.
1582 2007
1583C<Glib>'s memory usage is quite a bit higher, but it features a 2008C<Glib>'s memory usage is quite a bit higher, but it features a
1584faster callback invocation and overall ends up in the same class as 2009faster callback invocation and overall ends up in the same class as
1585C<Event>. However, Glib scales extremely badly, doubling the number of 2010C<Event>. However, Glib scales extremely badly, doubling the number of
1586watchers increases the processing time by more than a factor of four, 2011watchers increases the processing time by more than a factor of four,
1664it to another server. This includes deleting the old timeout and creating 2089it to another server. This includes deleting the old timeout and creating
1665a new one that moves the timeout into the future. 2090a new one that moves the timeout into the future.
1666 2091
1667=head3 Results 2092=head3 Results
1668 2093
1669 name sockets create request 2094 name sockets create request
1670 EV 20000 69.01 11.16 2095 EV 20000 69.01 11.16
1671 Perl 20000 73.32 35.87 2096 Perl 20000 73.32 35.87
2097 IOAsync 20000 157.00 98.14 epoll
2098 IOAsync 20000 159.31 616.06 poll
1672 Event 20000 212.62 257.32 2099 Event 20000 212.62 257.32
1673 Glib 20000 651.16 1896.30 2100 Glib 20000 651.16 1896.30
1674 POE 20000 349.67 12317.24 uses POE::Loop::Event 2101 POE 20000 349.67 12317.24 uses POE::Loop::Event
1675 2102
1676=head3 Discussion 2103=head3 Discussion
1677 2104
1678This benchmark I<does> measure scalability and overall performance of the 2105This benchmark I<does> measure scalability and overall performance of the
1679particular event loop. 2106particular event loop.
1681EV is again fastest. Since it is using epoll on my system, the setup time 2108EV is again fastest. Since it is using epoll on my system, the setup time
1682is relatively high, though. 2109is relatively high, though.
1683 2110
1684Perl surprisingly comes second. It is much faster than the C-based event 2111Perl surprisingly comes second. It is much faster than the C-based event
1685loops Event and Glib. 2112loops Event and Glib.
2113
2114IO::Async performs very well when using its epoll backend, and still quite
2115good compared to Glib when using its pure perl backend.
1686 2116
1687Event suffers from high setup time as well (look at its code and you will 2117Event suffers from high setup time as well (look at its code and you will
1688understand why). Callback invocation also has a high overhead compared to 2118understand why). Callback invocation also has a high overhead compared to
1689the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event 2119the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1690uses select or poll in basically all documented configurations. 2120uses select or poll in basically all documented configurations.
1753=item * C-based event loops perform very well with small number of 2183=item * C-based event loops perform very well with small number of
1754watchers, as the management overhead dominates. 2184watchers, as the management overhead dominates.
1755 2185
1756=back 2186=back
1757 2187
2188=head2 THE IO::Lambda BENCHMARK
2189
2190Recently I was told about the benchmark in the IO::Lambda manpage, which
2191could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
2192simply compares IO::Lambda with POE, and IO::Lambda looks better (which
2193shouldn't come as a surprise to anybody). As such, the benchmark is
2194fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
2195very optimal. But how would AnyEvent compare when used without the extra
2196baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
2197
2198The benchmark itself creates an echo-server, and then, for 500 times,
2199connects to the echo server, sends a line, waits for the reply, and then
2200creates the next connection. This is a rather bad benchmark, as it doesn't
2201test the efficiency of the framework or much non-blocking I/O, but it is a
2202benchmark nevertheless.
2203
2204 name runtime
2205 Lambda/select 0.330 sec
2206 + optimized 0.122 sec
2207 Lambda/AnyEvent 0.327 sec
2208 + optimized 0.138 sec
2209 Raw sockets/select 0.077 sec
2210 POE/select, components 0.662 sec
2211 POE/select, raw sockets 0.226 sec
2212 POE/select, optimized 0.404 sec
2213
2214 AnyEvent/select/nb 0.085 sec
2215 AnyEvent/EV/nb 0.068 sec
2216 +state machine 0.134 sec
2217
2218The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
2219benchmarks actually make blocking connects and use 100% blocking I/O,
2220defeating the purpose of an event-based solution. All of the newly
2221written AnyEvent benchmarks use 100% non-blocking connects (using
2222AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
2223resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
2224generally require a lot more bookkeeping and event handling than blocking
2225connects (which involve a single syscall only).
2226
2227The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
2228offers similar expressive power as POE and IO::Lambda, using conventional
2229Perl syntax. This means that both the echo server and the client are 100%
2230non-blocking, further placing it at a disadvantage.
2231
2232As you can see, the AnyEvent + EV combination even beats the
2233hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
2234backend easily beats IO::Lambda and POE.
2235
2236And even the 100% non-blocking version written using the high-level (and
2237slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda by a
2238large margin, even though it does all of DNS, tcp-connect and socket I/O
2239in a non-blocking way.
2240
2241The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
2242F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
2243part of the IO::lambda distribution and were used without any changes.
2244
1758 2245
1759=head1 SIGNALS 2246=head1 SIGNALS
1760 2247
1761AnyEvent currently installs handlers for these signals: 2248AnyEvent currently installs handlers for these signals:
1762 2249
1765=item SIGCHLD 2252=item SIGCHLD
1766 2253
1767A handler for C<SIGCHLD> is installed by AnyEvent's child watcher 2254A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
1768emulation for event loops that do not support them natively. Also, some 2255emulation for event loops that do not support them natively. Also, some
1769event loops install a similar handler. 2256event loops install a similar handler.
2257
2258Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
2259AnyEvent will reset it to default, to avoid losing child exit statuses.
1770 2260
1771=item SIGPIPE 2261=item SIGPIPE
1772 2262
1773A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef> 2263A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
1774when AnyEvent gets loaded. 2264when AnyEvent gets loaded.
1786 2276
1787=back 2277=back
1788 2278
1789=cut 2279=cut
1790 2280
2281undef $SIG{CHLD}
2282 if $SIG{CHLD} eq 'IGNORE';
2283
1791$SIG{PIPE} = sub { } 2284$SIG{PIPE} = sub { }
1792 unless defined $SIG{PIPE}; 2285 unless defined $SIG{PIPE};
2286
2287=head1 RECOMMENDED/OPTIONAL MODULES
2288
2289One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
2290it's built-in modules) are required to use it.
2291
2292That does not mean that AnyEvent won't take advantage of some additional
2293modules if they are installed.
2294
2295This section epxlains which additional modules will be used, and how they
2296affect AnyEvent's operetion.
2297
2298=over 4
2299
2300=item L<Async::Interrupt>
2301
2302This slightly arcane module is used to implement fast signal handling: To
2303my knowledge, there is no way to do completely race-free and quick
2304signal handling in pure perl. To ensure that signals still get
2305delivered, AnyEvent will start an interval timer to wake up perl (and
2306catch the signals) with some delay (default is 10 seconds, look for
2307C<$AnyEvent::MAX_SIGNAL_LATENCY>).
2308
2309If this module is available, then it will be used to implement signal
2310catching, which means that signals will not be delayed, and the event loop
2311will not be interrupted regularly, which is more efficient (And good for
2312battery life on laptops).
2313
2314This affects not just the pure-perl event loop, but also other event loops
2315that have no signal handling on their own (e.g. Glib, Tk, Qt).
2316
2317Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
2318and either employ their own workarounds (POE) or use AnyEvent's workaround
2319(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
2320does nothing for those backends.
2321
2322=item L<EV>
2323
2324This module isn't really "optional", as it is simply one of the backend
2325event loops that AnyEvent can use. However, it is simply the best event
2326loop available in terms of features, speed and stability: It supports
2327the AnyEvent API optimally, implements all the watcher types in XS, does
2328automatic timer adjustments even when no monotonic clock is available,
2329can take avdantage of advanced kernel interfaces such as C<epoll> and
2330C<kqueue>, and is the fastest backend I<by far>. You can even embed
2331L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
2332
2333=item L<Guard>
2334
2335The guard module, when used, will be used to implement
2336C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
2337lot less memory), but otherwise doesn't affect guard operation much. It is
2338purely used for performance.
2339
2340=item L<JSON> and L<JSON::XS>
2341
2342This module is required when you want to read or write JSON data via
2343L<AnyEvent::Handle>. It is also written in pure-perl, but can take
2344advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
2345
2346In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
2347installed.
2348
2349=item L<Net::SSLeay>
2350
2351Implementing TLS/SSL in Perl is certainly interesting, but not very
2352worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
2353the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
2354
2355=item L<Time::HiRes>
2356
2357This module is part of perl since release 5.008. It will be used when the
2358chosen event library does not come with a timing source on it's own. The
2359pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to
2360try to use a monotonic clock for timing stability.
2361
2362=back
1793 2363
1794 2364
1795=head1 FORK 2365=head1 FORK
1796 2366
1797Most event libraries are not fork-safe. The ones who are usually are 2367Most event libraries are not fork-safe. The ones who are usually are
1798because they rely on inefficient but fork-safe C<select> or C<poll> 2368because they rely on inefficient but fork-safe C<select> or C<poll>
1799calls. Only L<EV> is fully fork-aware. 2369calls. Only L<EV> is fully fork-aware.
1800 2370
1801If you have to fork, you must either do so I<before> creating your first 2371If you have to fork, you must either do so I<before> creating your first
1802watcher OR you must not use AnyEvent at all in the child. 2372watcher OR you must not use AnyEvent at all in the child OR you must do
2373something completely out of the scope of AnyEvent.
1803 2374
1804 2375
1805=head1 SECURITY CONSIDERATIONS 2376=head1 SECURITY CONSIDERATIONS
1806 2377
1807AnyEvent can be forced to load any event model via 2378AnyEvent can be forced to load any event model via
1819 use AnyEvent; 2390 use AnyEvent;
1820 2391
1821Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can 2392Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1822be used to probe what backend is used and gain other information (which is 2393be used to probe what backend is used and gain other information (which is
1823probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and 2394probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1824$ENV{PERL_ANYEGENT_STRICT}. 2395$ENV{PERL_ANYEVENT_STRICT}.
2396
2397Note that AnyEvent will remove I<all> environment variables starting with
2398C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
2399enabled.
1825 2400
1826 2401
1827=head1 BUGS 2402=head1 BUGS
1828 2403
1829Perl 5.8 has numerous memleaks that sometimes hit this module and are hard 2404Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1830to work around. If you suffer from memleaks, first upgrade to Perl 5.10 2405to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1831and check wether the leaks still show up. (Perl 5.10.0 has other annoying 2406and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1832mamleaks, such as leaking on C<map> and C<grep> but it is usually not as 2407memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1833pronounced). 2408pronounced).
1834 2409
1835 2410
1836=head1 SEE ALSO 2411=head1 SEE ALSO
1837 2412
1841L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. 2416L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1842 2417
1843Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, 2418Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1844L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, 2419L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1845L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, 2420L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1846L<AnyEvent::Impl::POE>. 2421L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>.
1847 2422
1848Non-blocking file handles, sockets, TCP clients and 2423Non-blocking file handles, sockets, TCP clients and
1849servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>. 2424servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1850 2425
1851Asynchronous DNS: L<AnyEvent::DNS>. 2426Asynchronous DNS: L<AnyEvent::DNS>.
1852 2427
1853Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, 2428Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>,
2429L<Coro::Event>,
1854 2430
1855Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. 2431Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>,
2432L<AnyEvent::HTTP>.
1856 2433
1857 2434
1858=head1 AUTHOR 2435=head1 AUTHOR
1859 2436
1860 Marc Lehmann <schmorp@schmorp.de> 2437 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines