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.173 by root, Mon Jul 21 03:47:22 2008 UTC vs.
Revision 1.309 by root, Sat Dec 26 08:59:35 2009 UTC

1=head1 NAME 1=head1 NAME
2 2
3AnyEvent - provide framework for multiple event loops 3AnyEvent - the DBI of event loop programming
4 4
5EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops 5EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt
6and POE are various supported event loops/environments.
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
52Repository>, 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.
159my variables are only visible after the statement in which they are 181my variables are only visible after the statement in which they are
160declared. 182declared.
161 183
162=head2 I/O WATCHERS 184=head2 I/O WATCHERS
163 185
186 $w = AnyEvent->io (
187 fh => <filehandle_or_fileno>,
188 poll => <"r" or "w">,
189 cb => <callback>,
190 );
191
164You can create an I/O watcher by calling the C<< AnyEvent->io >> method 192You can create an I/O watcher by calling the C<< AnyEvent->io >> method
165with the following mandatory key-value pairs as arguments: 193with the following mandatory key-value pairs as arguments:
166 194
167C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events 195C<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> 196for events (AnyEvent might or might not keep a reference to this file
197handle). Note that only file handles pointing to things for which
198non-blocking operation makes sense are allowed. This includes sockets,
199most character devices, pipes, fifos and so on, but not for example files
200or block devices.
201
169must be a string that is either C<r> or C<w>, which creates a watcher 202C<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 203watcher waiting for "r"eadable or "w"ritable events, respectively.
204
171callback to invoke each time the file handle becomes ready. 205C<cb> is the callback to invoke each time the file handle becomes ready.
172 206
173Although the callback might get passed parameters, their value and 207Although the callback might get passed parameters, their value and
174presence is undefined and you cannot rely on them. Portable AnyEvent 208presence is undefined and you cannot rely on them. Portable AnyEvent
175callbacks cannot use arguments passed to I/O watcher callbacks. 209callbacks cannot use arguments passed to I/O watcher callbacks.
176 210
191 undef $w; 225 undef $w;
192 }); 226 });
193 227
194=head2 TIME WATCHERS 228=head2 TIME WATCHERS
195 229
230 $w = AnyEvent->timer (after => <seconds>, cb => <callback>);
231
232 $w = AnyEvent->timer (
233 after => <fractional_seconds>,
234 interval => <fractional_seconds>,
235 cb => <callback>,
236 );
237
196You can create a time watcher by calling the C<< AnyEvent->timer >> 238You can create a time watcher by calling the C<< AnyEvent->timer >>
197method with the following mandatory arguments: 239method with the following mandatory arguments:
198 240
199C<after> specifies after how many seconds (fractional values are 241C<after> specifies after how many seconds (fractional values are
200supported) the callback should be invoked. C<cb> is the callback to invoke 242supported) the callback should be invoked. C<cb> is the callback to invoke
308In either case, if you care (and in most cases, you don't), then you 350In 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 351can get whatever behaviour you want with any event loop, by taking the
310difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into 352difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
311account. 353account.
312 354
355=item AnyEvent->now_update
356
357Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache
358the current time for each loop iteration (see the discussion of L<<
359AnyEvent->now >>, above).
360
361When a callback runs for a long time (or when the process sleeps), then
362this "current" time will differ substantially from the real time, which
363might affect timers and time-outs.
364
365When this is the case, you can call this method, which will update the
366event loop's idea of "current time".
367
368A typical example would be a script in a web server (e.g. C<mod_perl>) -
369when mod_perl executes the script, then the event loop will have the wrong
370idea about the "current time" (being potentially far in the past, when the
371script ran the last time). In that case you should arrange a call to C<<
372AnyEvent->now_update >> each time the web server process wakes up again
373(e.g. at the start of your script, or in a handler).
374
375Note that updating the time I<might> cause some events to be handled.
376
313=back 377=back
314 378
315=head2 SIGNAL WATCHERS 379=head2 SIGNAL WATCHERS
380
381 $w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
316 382
317You can watch for signals using a signal watcher, C<signal> is the signal 383You can watch for signals using a signal watcher, C<signal> is the signal
318I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl 384I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
319callback to be invoked whenever a signal occurs. 385callback to be invoked whenever a signal occurs.
320 386
326invocation, and callback invocation will be synchronous. Synchronous means 392invocation, and callback invocation will be synchronous. Synchronous means
327that it might take a while until the signal gets handled by the process, 393that it might take a while until the signal gets handled by the process,
328but it is guaranteed not to interrupt any other callbacks. 394but it is guaranteed not to interrupt any other callbacks.
329 395
330The main advantage of using these watchers is that you can share a signal 396The main advantage of using these watchers is that you can share a signal
331between multiple watchers. 397between multiple watchers, and AnyEvent will ensure that signals will not
398interrupt your program at bad times.
332 399
333This watcher might use C<%SIG>, so programs overwriting those signals 400This watcher might use C<%SIG> (depending on the event loop used),
334directly will likely not work correctly. 401so programs overwriting those signals directly will likely not work
402correctly.
335 403
336Example: exit on SIGINT 404Example: exit on SIGINT
337 405
338 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); 406 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
339 407
408=head3 Restart Behaviour
409
410While restart behaviour is up to the event loop implementation, most will
411not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's
412pure perl implementation).
413
414=head3 Safe/Unsafe Signals
415
416Perl signals can be either "safe" (synchronous to opcode handling) or
417"unsafe" (asynchronous) - the former might get delayed indefinitely, the
418latter might corrupt your memory.
419
420AnyEvent signal handlers are, in addition, synchronous to the event loop,
421i.e. they will not interrupt your running perl program but will only be
422called as part of the normal event handling (just like timer, I/O etc.
423callbacks, too).
424
425=head3 Signal Races, Delays and Workarounds
426
427Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
428callbacks to signals in a generic way, which is a pity, as you cannot
429do race-free signal handling in perl, requiring C libraries for
430this. AnyEvent will try to do it's best, which means in some cases,
431signals will be delayed. The maximum time a signal might be delayed is
432specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
433variable can be changed only before the first signal watcher is created,
434and should be left alone otherwise. This variable determines how often
435AnyEvent polls for signals (in case a wake-up was missed). Higher values
436will cause fewer spurious wake-ups, which is better for power and CPU
437saving.
438
439All these problems can be avoided by installing the optional
440L<Async::Interrupt> module, which works with most event loops. It will not
441work with inherently broken event loops such as L<Event> or L<Event::Lib>
442(and not with L<POE> currently, as POE does it's own workaround with
443one-second latency). For those, you just have to suffer the delays.
444
340=head2 CHILD PROCESS WATCHERS 445=head2 CHILD PROCESS WATCHERS
341 446
447 $w = AnyEvent->child (pid => <process id>, cb => <callback>);
448
342You can also watch on a child process exit and catch its exit status. 449You can also watch on a child process exit and catch its exit status.
343 450
344The child process is specified by the C<pid> argument (if set to C<0>, it 451The child process is specified by the C<pid> argument (one some backends,
345watches for any child process exit). The watcher will trigger as often 452using C<0> watches for any child process exit, on others this will
346as status change for the child are received. This works by installing a 453croak). The watcher will be triggered only when the child process has
347signal handler for C<SIGCHLD>. The callback will be called with the pid 454finished and an exit status is available, not on any trace events
348and exit status (as returned by waitpid), so unlike other watcher types, 455(stopped/continued).
349you I<can> rely on child watcher callback arguments. 456
457The callback will be called with the pid and exit status (as returned by
458waitpid), so unlike other watcher types, you I<can> rely on child watcher
459callback arguments.
460
461This watcher type works by installing a signal handler for C<SIGCHLD>,
462and since it cannot be shared, nothing else should use SIGCHLD or reap
463random child processes (waiting for specific child processes, e.g. inside
464C<system>, is just fine).
350 465
351There is a slight catch to child watchers, however: you usually start them 466There is a slight catch to child watchers, however: you usually start them
352I<after> the child process was created, and this means the process could 467I<after> the child process was created, and this means the process could
353have exited already (and no SIGCHLD will be sent anymore). 468have exited already (and no SIGCHLD will be sent anymore).
354 469
355Not all event models handle this correctly (POE doesn't), but even for 470Not all event models handle this correctly (neither POE nor IO::Async do,
471see their AnyEvent::Impl manpages for details), but even for event models
356event models that I<do> handle this correctly, they usually need to be 472that I<do> handle this correctly, they usually need to be loaded before
357loaded before the process exits (i.e. before you fork in the first place). 473the process exits (i.e. before you fork in the first place). AnyEvent's
474pure perl event loop handles all cases correctly regardless of when you
475start the watcher.
358 476
359This means you cannot create a child watcher as the very first thing in an 477This means you cannot create a child watcher as the very first
360AnyEvent program, you I<have> to create at least one watcher before you 478thing in an AnyEvent program, you I<have> to create at least one
361C<fork> the child (alternatively, you can call C<AnyEvent::detect>). 479watcher before you C<fork> the child (alternatively, you can call
480C<AnyEvent::detect>).
481
482As most event loops do not support waiting for child events, they will be
483emulated by AnyEvent in most cases, in which the latency and race problems
484mentioned in the description of signal watchers apply.
362 485
363Example: fork a process and wait for it 486Example: fork a process and wait for it
364 487
365 my $done = AnyEvent->condvar; 488 my $done = AnyEvent->condvar;
366 489
376 ); 499 );
377 500
378 # do something else, then wait for process exit 501 # do something else, then wait for process exit
379 $done->recv; 502 $done->recv;
380 503
504=head2 IDLE WATCHERS
505
506 $w = AnyEvent->idle (cb => <callback>);
507
508Repeatedly invoke the callback after the process becomes idle, until
509either the watcher is destroyed or new events have been detected.
510
511Idle watchers are useful when there is a need to do something, but it
512is not so important (or wise) to do it instantly. The callback will be
513invoked only when there is "nothing better to do", which is usually
514defined as "all outstanding events have been handled and no new events
515have been detected". That means that idle watchers ideally get invoked
516when the event loop has just polled for new events but none have been
517detected. Instead of blocking to wait for more events, the idle watchers
518will be invoked.
519
520Unfortunately, most event loops do not really support idle watchers (only
521EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
522will simply call the callback "from time to time".
523
524Example: read lines from STDIN, but only process them when the
525program is otherwise idle:
526
527 my @lines; # read data
528 my $idle_w;
529 my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
530 push @lines, scalar <STDIN>;
531
532 # start an idle watcher, if not already done
533 $idle_w ||= AnyEvent->idle (cb => sub {
534 # handle only one line, when there are lines left
535 if (my $line = shift @lines) {
536 print "handled when idle: $line";
537 } else {
538 # otherwise disable the idle watcher again
539 undef $idle_w;
540 }
541 });
542 });
543
381=head2 CONDITION VARIABLES 544=head2 CONDITION VARIABLES
545
546 $cv = AnyEvent->condvar;
547
548 $cv->send (<list>);
549 my @res = $cv->recv;
382 550
383If you are familiar with some event loops you will know that all of them 551If you are familiar with some event loops you will know that all of them
384require you to run some blocking "loop", "run" or similar function that 552require you to run some blocking "loop", "run" or similar function that
385will actively watch for new events and call your callbacks. 553will actively watch for new events and call your callbacks.
386 554
387AnyEvent is different, it expects somebody else to run the event loop and 555AnyEvent is slightly different: it expects somebody else to run the event
388will only block when necessary (usually when told by the user). 556loop and will only block when necessary (usually when told by the user).
389 557
390The instrument to do that is called a "condition variable", so called 558The instrument to do that is called a "condition variable", so called
391because they represent a condition that must become true. 559because they represent a condition that must become true.
392 560
561Now is probably a good time to look at the examples further below.
562
393Condition variables can be created by calling the C<< AnyEvent->condvar 563Condition variables can be created by calling the C<< AnyEvent->condvar
394
395>> method, usually without arguments. The only argument pair allowed is 564>> method, usually without arguments. The only argument pair allowed is
396
397C<cb>, which specifies a callback to be called when the condition variable 565C<cb>, which specifies a callback to be called when the condition variable
398becomes true, with the condition variable as the first argument (but not 566becomes true, with the condition variable as the first argument (but not
399the results). 567the results).
400 568
401After creation, the condition variable is "false" until it becomes "true" 569After creation, the condition variable is "false" until it becomes "true"
406Condition variables are similar to callbacks, except that you can 574Condition variables are similar to callbacks, except that you can
407optionally wait for them. They can also be called merge points - points 575optionally wait for them. They can also be called merge points - points
408in time where multiple outstanding events have been processed. And yet 576in time where multiple outstanding events have been processed. And yet
409another way to call them is transactions - each condition variable can be 577another way to call them is transactions - each condition variable can be
410used to represent a transaction, which finishes at some point and delivers 578used to represent a transaction, which finishes at some point and delivers
411a result. 579a result. And yet some people know them as "futures" - a promise to
580compute/deliver something that you can wait for.
412 581
413Condition variables are very useful to signal that something has finished, 582Condition variables are very useful to signal that something has finished,
414for example, if you write a module that does asynchronous http requests, 583for example, if you write a module that does asynchronous http requests,
415then a condition variable would be the ideal candidate to signal the 584then a condition variable would be the ideal candidate to signal the
416availability of results. The user can either act when the callback is 585availability of results. The user can either act when the callback is
450 after => 1, 619 after => 1,
451 cb => sub { $result_ready->send }, 620 cb => sub { $result_ready->send },
452 ); 621 );
453 622
454 # this "blocks" (while handling events) till the callback 623 # this "blocks" (while handling events) till the callback
455 # calls send 624 # calls ->send
456 $result_ready->recv; 625 $result_ready->recv;
457 626
458Example: wait for a timer, but take advantage of the fact that 627Example: wait for a timer, but take advantage of the fact that condition
459condition variables are also code references. 628variables are also callable directly.
460 629
461 my $done = AnyEvent->condvar; 630 my $done = AnyEvent->condvar;
462 my $delay = AnyEvent->timer (after => 5, cb => $done); 631 my $delay = AnyEvent->timer (after => 5, cb => $done);
463 $done->recv; 632 $done->recv;
464 633
470 639
471 ... 640 ...
472 641
473 my @info = $couchdb->info->recv; 642 my @info = $couchdb->info->recv;
474 643
475And this is how you would just ste a callback to be called whenever the 644And this is how you would just set a callback to be called whenever the
476results are available: 645results are available:
477 646
478 $couchdb->info->cb (sub { 647 $couchdb->info->cb (sub {
479 my @info = $_[0]->recv; 648 my @info = $_[0]->recv;
480 }); 649 });
498immediately from within send. 667immediately from within send.
499 668
500Any arguments passed to the C<send> call will be returned by all 669Any arguments passed to the C<send> call will be returned by all
501future C<< ->recv >> calls. 670future C<< ->recv >> calls.
502 671
503Condition variables are overloaded so one can call them directly 672Condition variables are overloaded so one can call them directly (as if
504(as a code reference). Calling them directly is the same as calling 673they were a code reference). Calling them directly is the same as calling
505C<send>. Note, however, that many C-based event loops do not handle 674C<send>.
506overloading, so as tempting as it may be, passing a condition variable
507instead of a callback does not work. Both the pure perl and EV loops
508support overloading, however, as well as all functions that use perl to
509invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
510example).
511 675
512=item $cv->croak ($error) 676=item $cv->croak ($error)
513 677
514Similar to send, but causes all call's to C<< ->recv >> to invoke 678Similar to send, but causes all call's to C<< ->recv >> to invoke
515C<Carp::croak> with the given error message/object/scalar. 679C<Carp::croak> with the given error message/object/scalar.
516 680
517This can be used to signal any errors to the condition variable 681This can be used to signal any errors to the condition variable
518user/consumer. 682user/consumer. Doing it this way instead of calling C<croak> directly
683delays the error detetcion, but has the overwhelmign advantage that it
684diagnoses the error at the place where the result is expected, and not
685deep in some event clalback without connection to the actual code causing
686the problem.
519 687
520=item $cv->begin ([group callback]) 688=item $cv->begin ([group callback])
521 689
522=item $cv->end 690=item $cv->end
523
524These two methods are EXPERIMENTAL and MIGHT CHANGE.
525 691
526These two methods can be used to combine many transactions/events into 692These two methods can be used to combine many transactions/events into
527one. For example, a function that pings many hosts in parallel might want 693one. For example, a function that pings many hosts in parallel might want
528to use a condition variable for the whole process. 694to use a condition variable for the whole process.
529 695
530Every call to C<< ->begin >> will increment a counter, and every call to 696Every call to C<< ->begin >> will increment a counter, and every call to
531C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end 697C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
532>>, the (last) callback passed to C<begin> will be executed. That callback 698>>, the (last) callback passed to C<begin> will be executed, passing the
533is I<supposed> to call C<< ->send >>, but that is not required. If no 699condvar as first argument. That callback is I<supposed> to call C<< ->send
534callback was set, C<send> will be called without any arguments. 700>>, but that is not required. If no group callback was set, C<send> will
701be called without any arguments.
535 702
536Let's clarify this with the ping example: 703You can think of C<< $cv->send >> giving you an OR condition (one call
704sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
705condition (all C<begin> calls must be C<end>'ed before the condvar sends).
706
707Let's start with a simple example: you have two I/O watchers (for example,
708STDOUT and STDERR for a program), and you want to wait for both streams to
709close before activating a condvar:
537 710
538 my $cv = AnyEvent->condvar; 711 my $cv = AnyEvent->condvar;
539 712
713 $cv->begin; # first watcher
714 my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
715 defined sysread $fh1, my $buf, 4096
716 or $cv->end;
717 });
718
719 $cv->begin; # second watcher
720 my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
721 defined sysread $fh2, my $buf, 4096
722 or $cv->end;
723 });
724
725 $cv->recv;
726
727This works because for every event source (EOF on file handle), there is
728one call to C<begin>, so the condvar waits for all calls to C<end> before
729sending.
730
731The ping example mentioned above is slightly more complicated, as the
732there are results to be passwd back, and the number of tasks that are
733begung can potentially be zero:
734
735 my $cv = AnyEvent->condvar;
736
540 my %result; 737 my %result;
541 $cv->begin (sub { $cv->send (\%result) }); 738 $cv->begin (sub { shift->send (\%result) });
542 739
543 for my $host (@list_of_hosts) { 740 for my $host (@list_of_hosts) {
544 $cv->begin; 741 $cv->begin;
545 ping_host_then_call_callback $host, sub { 742 ping_host_then_call_callback $host, sub {
546 $result{$host} = ...; 743 $result{$host} = ...;
561loop, which serves two important purposes: first, it sets the callback 758loop, which serves two important purposes: first, it sets the callback
562to be called once the counter reaches C<0>, and second, it ensures that 759to be called once the counter reaches C<0>, and second, it ensures that
563C<send> is called even when C<no> hosts are being pinged (the loop 760C<send> is called even when C<no> hosts are being pinged (the loop
564doesn't execute once). 761doesn't execute once).
565 762
566This is the general pattern when you "fan out" into multiple subrequests: 763This is the general pattern when you "fan out" into multiple (but
567use an outer C<begin>/C<end> pair to set the callback and ensure C<end> 764potentially none) subrequests: use an outer C<begin>/C<end> pair to set
568is called at least once, and then, for each subrequest you start, call 765the callback and ensure C<end> is called at least once, and then, for each
569C<begin> and for each subrequest you finish, call C<end>. 766subrequest you start, call C<begin> and for each subrequest you finish,
767call C<end>.
570 768
571=back 769=back
572 770
573=head3 METHODS FOR CONSUMERS 771=head3 METHODS FOR CONSUMERS
574 772
590function will call C<croak>. 788function will call C<croak>.
591 789
592In list context, all parameters passed to C<send> will be returned, 790In list context, all parameters passed to C<send> will be returned,
593in scalar context only the first one will be returned. 791in scalar context only the first one will be returned.
594 792
793Note that doing a blocking wait in a callback is not supported by any
794event loop, that is, recursive invocation of a blocking C<< ->recv
795>> is not allowed, and the C<recv> call will C<croak> if such a
796condition is detected. This condition can be slightly loosened by using
797L<Coro::AnyEvent>, which allows you to do a blocking C<< ->recv >> from
798any thread that doesn't run the event loop itself.
799
595Not all event models support a blocking wait - some die in that case 800Not all event models support a blocking wait - some die in that case
596(programs might want to do that to stay interactive), so I<if you are 801(programs might want to do that to stay interactive), so I<if you are
597using this from a module, never require a blocking wait>, but let the 802using this from a module, never require a blocking wait>. Instead, let the
598caller decide whether the call will block or not (for example, by coupling 803caller decide whether the call will block or not (for example, by coupling
599condition variables with some kind of request results and supporting 804condition variables with some kind of request results and supporting
600callbacks so the caller knows that getting the result will not block, 805callbacks so the caller knows that getting the result will not block,
601while still supporting blocking waits if the caller so desires). 806while still supporting blocking waits if the caller so desires).
602 807
603Another reason I<never> to C<< ->recv >> in a module is that you cannot
604sensibly have two C<< ->recv >>'s in parallel, as that would require
605multiple interpreters or coroutines/threads, none of which C<AnyEvent>
606can supply.
607
608The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
609fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
610versions and also integrates coroutines into AnyEvent, making blocking
611C<< ->recv >> calls perfectly safe as long as they are done from another
612coroutine (one that doesn't run the event loop).
613
614You can ensure that C<< -recv >> never blocks by setting a callback and 808You can ensure that C<< -recv >> never blocks by setting a callback and
615only calling C<< ->recv >> from within that callback (or at a later 809only calling C<< ->recv >> from within that callback (or at a later
616time). This will work even when the event loop does not support blocking 810time). This will work even when the event loop does not support blocking
617waits otherwise. 811waits otherwise.
618 812
624=item $cb = $cv->cb ($cb->($cv)) 818=item $cb = $cv->cb ($cb->($cv))
625 819
626This is a mutator function that returns the callback set and optionally 820This is a mutator function that returns the callback set and optionally
627replaces it before doing so. 821replaces it before doing so.
628 822
629The callback will be called when the condition becomes "true", i.e. when 823The callback will be called when the condition becomes (or already was)
630C<send> or C<croak> are called, with the only argument being the condition 824"true", i.e. when C<send> or C<croak> are called (or were called), with
631variable itself. Calling C<recv> inside the callback or at any later time 825the only argument being the condition variable itself. Calling C<recv>
632is guaranteed not to block. 826inside the callback or at any later time is guaranteed not to block.
633 827
634=back 828=back
635 829
830=head1 SUPPORTED EVENT LOOPS/BACKENDS
831
832The available backend classes are (every class has its own manpage):
833
834=over 4
835
836=item Backends that are autoprobed when no other event loop can be found.
837
838EV is the preferred backend when no other event loop seems to be in
839use. If EV is not installed, then AnyEvent will fall back to its own
840pure-perl implementation, which is available everywhere as it comes with
841AnyEvent itself.
842
843 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
844 AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
845
846=item Backends that are transparently being picked up when they are used.
847
848These will be used when they are currently loaded when the first watcher
849is created, in which case it is assumed that the application is using
850them. This means that AnyEvent will automatically pick the right backend
851when the main program loads an event module before anything starts to
852create watchers. Nothing special needs to be done by the main program.
853
854 AnyEvent::Impl::Event based on Event, very stable, few glitches.
855 AnyEvent::Impl::Glib based on Glib, slow but very stable.
856 AnyEvent::Impl::Tk based on Tk, very broken.
857 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
858 AnyEvent::Impl::POE based on POE, very slow, some limitations.
859 AnyEvent::Impl::Irssi used when running within irssi.
860
861=item Backends with special needs.
862
863Qt requires the Qt::Application to be instantiated first, but will
864otherwise be picked up automatically. As long as the main program
865instantiates the application before any AnyEvent watchers are created,
866everything should just work.
867
868 AnyEvent::Impl::Qt based on Qt.
869
870Support for IO::Async can only be partial, as it is too broken and
871architecturally limited to even support the AnyEvent API. It also
872is the only event loop that needs the loop to be set explicitly, so
873it can only be used by a main program knowing about AnyEvent. See
874L<AnyEvent::Impl::Async> for the gory details.
875
876 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
877
878=item Event loops that are indirectly supported via other backends.
879
880Some event loops can be supported via other modules:
881
882There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
883
884B<WxWidgets> has no support for watching file handles. However, you can
885use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
886polls 20 times per second, which was considered to be too horrible to even
887consider for AnyEvent.
888
889B<Prima> is not supported as nobody seems to be using it, but it has a POE
890backend, so it can be supported through POE.
891
892AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
893load L<POE> when detecting them, in the hope that POE will pick them up,
894in which case everything will be automatic.
895
896=back
897
636=head1 GLOBAL VARIABLES AND FUNCTIONS 898=head1 GLOBAL VARIABLES AND FUNCTIONS
637 899
900These are not normally required to use AnyEvent, but can be useful to
901write AnyEvent extension modules.
902
638=over 4 903=over 4
639 904
640=item $AnyEvent::MODEL 905=item $AnyEvent::MODEL
641 906
642Contains C<undef> until the first watcher is being created. Then it 907Contains C<undef> until the first watcher is being created, before the
908backend has been autodetected.
909
643contains the event model that is being used, which is the name of the 910Afterwards it contains the event model that is being used, which is the
644Perl class implementing the model. This class is usually one of the 911name of the Perl class implementing the model. This class is usually one
645C<AnyEvent::Impl:xxx> modules, but can be any other class in the case 912of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the
646AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). 913case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
647 914will be C<urxvt::anyevent>).
648The known classes so far are:
649
650 AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
651 AnyEvent::Impl::Event based on Event, second best choice.
652 AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
653 AnyEvent::Impl::Glib based on Glib, third-best choice.
654 AnyEvent::Impl::Tk based on Tk, very bad choice.
655 AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
656 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
657 AnyEvent::Impl::POE based on POE, not generic enough for full support.
658
659There is no support for WxWidgets, as WxWidgets has no support for
660watching file handles. However, you can use WxWidgets through the
661POE Adaptor, as POE has a Wx backend that simply polls 20 times per
662second, which was considered to be too horrible to even consider for
663AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
664it's adaptor.
665
666AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
667autodetecting them.
668 915
669=item AnyEvent::detect 916=item AnyEvent::detect
670 917
671Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 918Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
672if necessary. You should only call this function right before you would 919if necessary. You should only call this function right before you would
673have created an AnyEvent watcher anyway, that is, as late as possible at 920have created an AnyEvent watcher anyway, that is, as late as possible at
674runtime. 921runtime, and not e.g. while initialising of your module.
922
923If you need to do some initialisation before AnyEvent watchers are
924created, use C<post_detect>.
675 925
676=item $guard = AnyEvent::post_detect { BLOCK } 926=item $guard = AnyEvent::post_detect { BLOCK }
677 927
678Arranges for the code block to be executed as soon as the event model is 928Arranges for the code block to be executed as soon as the event model is
679autodetected (or immediately if this has already happened). 929autodetected (or immediately if this has already happened).
680 930
931The block will be executed I<after> the actual backend has been detected
932(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
933created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
934other initialisations - see the sources of L<AnyEvent::Strict> or
935L<AnyEvent::AIO> to see how this is used.
936
937The most common usage is to create some global watchers, without forcing
938event module detection too early, for example, L<AnyEvent::AIO> creates
939and installs the global L<IO::AIO> watcher in a C<post_detect> block to
940avoid autodetecting the event module at load time.
941
681If called in scalar or list context, then it creates and returns an object 942If called in scalar or list context, then it creates and returns an object
682that automatically removes the callback again when it is destroyed. See 943that automatically removes the callback again when it is destroyed (or
944C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
683L<Coro::BDB> for a case where this is useful. 945a case where this is useful.
946
947Example: Create a watcher for the IO::AIO module and store it in
948C<$WATCHER>. Only do so after the event loop is initialised, though.
949
950 our WATCHER;
951
952 my $guard = AnyEvent::post_detect {
953 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
954 };
955
956 # the ||= is important in case post_detect immediately runs the block,
957 # as to not clobber the newly-created watcher. assigning both watcher and
958 # post_detect guard to the same variable has the advantage of users being
959 # able to just C<undef $WATCHER> if the watcher causes them grief.
960
961 $WATCHER ||= $guard;
684 962
685=item @AnyEvent::post_detect 963=item @AnyEvent::post_detect
686 964
687If there are any code references in this array (you can C<push> to it 965If there are any code references in this array (you can C<push> to it
688before or after loading AnyEvent), then they will called directly after 966before or after loading AnyEvent), then they will called directly after
689the event loop has been chosen. 967the event loop has been chosen.
690 968
691You should check C<$AnyEvent::MODEL> before adding to this array, though: 969You should check C<$AnyEvent::MODEL> before adding to this array, though:
692if it contains a true value then the event loop has already been detected, 970if it is defined then the event loop has already been detected, and the
693and the array will be ignored. 971array will be ignored.
694 972
695Best use C<AnyEvent::post_detect { BLOCK }> instead. 973Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
974it, as it takes care of these details.
975
976This variable is mainly useful for modules that can do something useful
977when AnyEvent is used and thus want to know when it is initialised, but do
978not need to even load it by default. This array provides the means to hook
979into AnyEvent passively, without loading it.
980
981Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
982together, you could put this into Coro (this is the actual code used by
983Coro to accomplish this):
984
985 if (defined $AnyEvent::MODEL) {
986 # AnyEvent already initialised, so load Coro::AnyEvent
987 require Coro::AnyEvent;
988 } else {
989 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
990 # as soon as it is
991 push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
992 }
696 993
697=back 994=back
698 995
699=head1 WHAT TO DO IN A MODULE 996=head1 WHAT TO DO IN A MODULE
700 997
755 1052
756 1053
757=head1 OTHER MODULES 1054=head1 OTHER MODULES
758 1055
759The following is a non-exhaustive list of additional modules that use 1056The following is a non-exhaustive list of additional modules that use
760AnyEvent and can therefore be mixed easily with other AnyEvent modules 1057AnyEvent as a client and can therefore be mixed easily with other AnyEvent
761in the same program. Some of the modules come with AnyEvent, some are 1058modules and other event loops in the same program. Some of the modules
762available via CPAN. 1059come with AnyEvent, most are available via CPAN.
763 1060
764=over 4 1061=over 4
765 1062
766=item L<AnyEvent::Util> 1063=item L<AnyEvent::Util>
767 1064
776 1073
777=item L<AnyEvent::Handle> 1074=item L<AnyEvent::Handle>
778 1075
779Provide read and write buffers, manages watchers for reads and writes, 1076Provide read and write buffers, manages watchers for reads and writes,
780supports raw and formatted I/O, I/O queued and fully transparent and 1077supports raw and formatted I/O, I/O queued and fully transparent and
781non-blocking SSL/TLS. 1078non-blocking SSL/TLS (via L<AnyEvent::TLS>.
782 1079
783=item L<AnyEvent::DNS> 1080=item L<AnyEvent::DNS>
784 1081
785Provides rich asynchronous DNS resolver capabilities. 1082Provides rich asynchronous DNS resolver capabilities.
786 1083
814 1111
815=item L<AnyEvent::GPSD> 1112=item L<AnyEvent::GPSD>
816 1113
817A non-blocking interface to gpsd, a daemon delivering GPS information. 1114A non-blocking interface to gpsd, a daemon delivering GPS information.
818 1115
1116=item L<AnyEvent::IRC>
1117
1118AnyEvent based IRC client module family (replacing the older Net::IRC3).
1119
1120=item L<AnyEvent::XMPP>
1121
1122AnyEvent based XMPP (Jabber protocol) module family (replacing the older
1123Net::XMPP2>.
1124
819=item L<AnyEvent::IGS> 1125=item L<AnyEvent::IGS>
820 1126
821A non-blocking interface to the Internet Go Server protocol (used by 1127A non-blocking interface to the Internet Go Server protocol (used by
822L<App::IGS>). 1128L<App::IGS>).
823 1129
824=item L<Net::IRC3>
825
826AnyEvent based IRC client module family.
827
828=item L<Net::XMPP2>
829
830AnyEvent based XMPP (Jabber protocol) module family.
831
832=item L<Net::FCP> 1130=item L<Net::FCP>
833 1131
834AnyEvent-based implementation of the Freenet Client Protocol, birthplace 1132AnyEvent-based implementation of the Freenet Client Protocol, birthplace
835of AnyEvent. 1133of AnyEvent.
836 1134
840 1138
841=item L<Coro> 1139=item L<Coro>
842 1140
843Has special support for AnyEvent via L<Coro::AnyEvent>. 1141Has special support for AnyEvent via L<Coro::AnyEvent>.
844 1142
845=item L<IO::Lambda>
846
847The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
848
849=back 1143=back
850 1144
851=cut 1145=cut
852 1146
853package AnyEvent; 1147package AnyEvent;
854 1148
855no warnings; 1149# basically a tuned-down version of common::sense
856use strict; 1150sub common_sense {
1151 # from common:.sense 1.0
1152 ${^WARNING_BITS} = "\xfc\x3f\x33\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x00";
1153 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
1154 $^H |= 0x00000600;
1155}
857 1156
1157BEGIN { AnyEvent::common_sense }
1158
858use Carp; 1159use Carp ();
859 1160
860our $VERSION = 4.22; 1161our $VERSION = '5.23';
861our $MODEL; 1162our $MODEL;
862 1163
863our $AUTOLOAD; 1164our $AUTOLOAD;
864our @ISA; 1165our @ISA;
865 1166
866our @REGISTRY; 1167our @REGISTRY;
867 1168
868our $WIN32; 1169our $VERBOSE;
869 1170
870BEGIN { 1171BEGIN {
871 my $win32 = ! ! ($^O =~ /mswin32/i); 1172 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
872 eval "sub WIN32(){ $win32 }"; 1173 eval "sub TAINT(){ " . (${^TAINT}*1) . " }";
873}
874 1174
1175 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
1176 if ${^TAINT};
1177
875our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 1178 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
1179
1180}
1181
1182our $MAX_SIGNAL_LATENCY = 10;
876 1183
877our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred 1184our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
878 1185
879{ 1186{
880 my $idx; 1187 my $idx;
882 for reverse split /\s*,\s*/, 1189 for reverse split /\s*,\s*/,
883 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; 1190 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
884} 1191}
885 1192
886my @models = ( 1193my @models = (
887 [EV:: => AnyEvent::Impl::EV::], 1194 [EV:: => AnyEvent::Impl::EV:: , 1],
888 [Event:: => AnyEvent::Impl::Event::],
889 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 1195 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1],
890 # everything below here will not be autoprobed 1196 # everything below here will not (normally) be autoprobed
891 # as the pureperl backend should work everywhere 1197 # as the pureperl backend should work everywhere
892 # and is usually faster 1198 # and is usually faster
1199 [Event:: => AnyEvent::Impl::Event::, 1],
1200 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
1201 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
1202 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
893 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles 1203 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
894 [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
895 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
896 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program 1204 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program
897 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 1205 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
898 [Wx:: => AnyEvent::Impl::POE::], 1206 [Wx:: => AnyEvent::Impl::POE::],
899 [Prima:: => AnyEvent::Impl::POE::], 1207 [Prima:: => AnyEvent::Impl::POE::],
1208 # IO::Async is just too broken - we would need workarounds for its
1209 # byzantine signal and broken child handling, among others.
1210 # IO::Async is rather hard to detect, as it doesn't have any
1211 # obvious default class.
1212 [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
1213 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
1214 [IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
1215 [AnyEvent::Impl::IOAsync:: => AnyEvent::Impl::IOAsync::], # requires special main program
900); 1216);
901 1217
902our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); 1218our %method = map +($_ => 1),
1219 qw(io timer time now now_update signal child idle condvar one_event DESTROY);
903 1220
904our @post_detect; 1221our @post_detect;
905 1222
906sub post_detect(&) { 1223sub post_detect(&) {
907 my ($cb) = @_; 1224 my ($cb) = @_;
908 1225
909 if ($MODEL) { 1226 if ($MODEL) {
910 $cb->(); 1227 $cb->();
911 1228
912 1 1229 undef
913 } else { 1230 } else {
914 push @post_detect, $cb; 1231 push @post_detect, $cb;
915 1232
916 defined wantarray 1233 defined wantarray
917 ? bless \$cb, "AnyEvent::Util::PostDetect" 1234 ? bless \$cb, "AnyEvent::Util::postdetect"
918 : () 1235 : ()
919 } 1236 }
920} 1237}
921 1238
922sub AnyEvent::Util::PostDetect::DESTROY { 1239sub AnyEvent::Util::postdetect::DESTROY {
923 @post_detect = grep $_ != ${$_[0]}, @post_detect; 1240 @post_detect = grep $_ != ${$_[0]}, @post_detect;
924} 1241}
925 1242
926sub detect() { 1243sub detect() {
927 unless ($MODEL) { 1244 unless ($MODEL) {
928 no strict 'refs';
929 local $SIG{__DIE__}; 1245 local $SIG{__DIE__};
930 1246
931 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 1247 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
932 my $model = "AnyEvent::Impl::$1"; 1248 my $model = "AnyEvent::Impl::$1";
933 if (eval "require $model") { 1249 if (eval "require $model") {
934 $MODEL = $model; 1250 $MODEL = $model;
935 warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1; 1251 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
936 } else { 1252 } else {
937 warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose; 1253 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
938 } 1254 }
939 } 1255 }
940 1256
941 # check for already loaded models 1257 # check for already loaded models
942 unless ($MODEL) { 1258 unless ($MODEL) {
943 for (@REGISTRY, @models) { 1259 for (@REGISTRY, @models) {
944 my ($package, $model) = @$_; 1260 my ($package, $model) = @$_;
945 if (${"$package\::VERSION"} > 0) { 1261 if (${"$package\::VERSION"} > 0) {
946 if (eval "require $model") { 1262 if (eval "require $model") {
947 $MODEL = $model; 1263 $MODEL = $model;
948 warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1; 1264 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
949 last; 1265 last;
950 } 1266 }
951 } 1267 }
952 } 1268 }
953 1269
954 unless ($MODEL) { 1270 unless ($MODEL) {
955 # try to load a model 1271 # try to autoload a model
956
957 for (@REGISTRY, @models) { 1272 for (@REGISTRY, @models) {
958 my ($package, $model) = @$_; 1273 my ($package, $model, $autoload) = @$_;
1274 if (
1275 $autoload
959 if (eval "require $package" 1276 and eval "require $package"
960 and ${"$package\::VERSION"} > 0 1277 and ${"$package\::VERSION"} > 0
961 and eval "require $model") { 1278 and eval "require $model"
1279 ) {
962 $MODEL = $model; 1280 $MODEL = $model;
963 warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1; 1281 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
964 last; 1282 last;
965 } 1283 }
966 } 1284 }
967 1285
968 $MODEL 1286 $MODEL
969 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib."; 1287 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n";
970 } 1288 }
971 } 1289 }
972 1290
973 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 1291 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
974 1292
984 1302
985sub AUTOLOAD { 1303sub AUTOLOAD {
986 (my $func = $AUTOLOAD) =~ s/.*://; 1304 (my $func = $AUTOLOAD) =~ s/.*://;
987 1305
988 $method{$func} 1306 $method{$func}
989 or croak "$func: not a valid method for AnyEvent objects"; 1307 or Carp::croak "$func: not a valid method for AnyEvent objects";
990 1308
991 detect unless $MODEL; 1309 detect unless $MODEL;
992 1310
993 my $class = shift; 1311 my $class = shift;
994 $class->$func (@_); 1312 $class->$func (@_);
995} 1313}
996 1314
997# utility function to dup a filehandle. this is used by many backends 1315# utility function to dup a filehandle. this is used by many backends
998# to support binding more than one watcher per filehandle (they usually 1316# to support binding more than one watcher per filehandle (they usually
999# allow only one watcher per fd, so we dup it to get a different one). 1317# allow only one watcher per fd, so we dup it to get a different one).
1000sub _dupfh($$$$) { 1318sub _dupfh($$;$$) {
1001 my ($poll, $fh, $r, $w) = @_; 1319 my ($poll, $fh, $r, $w) = @_;
1002 1320
1003 require Fcntl;
1004
1005 # cygwin requires the fh mode to be matching, unix doesn't 1321 # cygwin requires the fh mode to be matching, unix doesn't
1006 my ($rw, $mode) = $poll eq "r" ? ($r, "<") 1322 my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
1007 : $poll eq "w" ? ($w, ">")
1008 : Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1009 1323
1010 open my $fh2, "$mode&" . fileno $fh 1324 open my $fh2, $mode, $fh
1011 or die "cannot dup() filehandle: $!"; 1325 or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
1012 1326
1013 # we assume CLOEXEC is already set by perl in all important cases 1327 # we assume CLOEXEC is already set by perl in all important cases
1014 1328
1015 ($fh2, $rw) 1329 ($fh2, $rw)
1016} 1330}
1017 1331
1332=head1 SIMPLIFIED AE API
1333
1334Starting with version 5.0, AnyEvent officially supports a second, much
1335simpler, API that is designed to reduce the calling, typing and memory
1336overhead.
1337
1338See the L<AE> manpage for details.
1339
1340=cut
1341
1342package AE;
1343
1344our $VERSION = $AnyEvent::VERSION;
1345
1346sub io($$$) {
1347 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
1348}
1349
1350sub timer($$$) {
1351 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
1352}
1353
1354sub signal($$) {
1355 AnyEvent->signal (signal => $_[0], cb => $_[1])
1356}
1357
1358sub child($$) {
1359 AnyEvent->child (pid => $_[0], cb => $_[1])
1360}
1361
1362sub idle($) {
1363 AnyEvent->idle (cb => $_[0])
1364}
1365
1366sub cv(;&) {
1367 AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
1368}
1369
1370sub now() {
1371 AnyEvent->now
1372}
1373
1374sub now_update() {
1375 AnyEvent->now_update
1376}
1377
1378sub time() {
1379 AnyEvent->time
1380}
1381
1018package AnyEvent::Base; 1382package AnyEvent::Base;
1019 1383
1020# default implementation for now and time 1384# default implementations for many methods
1021 1385
1022use Time::HiRes (); 1386sub _time() {
1387 # probe for availability of Time::HiRes
1388 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
1389 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
1390 *_time = \&Time::HiRes::time;
1391 # if (eval "use POSIX (); (POSIX::times())...
1392 } else {
1393 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
1394 *_time = sub { time }; # epic fail
1395 }
1023 1396
1024sub time { Time::HiRes::time } 1397 &_time
1025sub now { Time::HiRes::time } 1398}
1399
1400sub time { _time }
1401sub now { _time }
1402sub now_update { }
1026 1403
1027# default implementation for ->condvar 1404# default implementation for ->condvar
1028 1405
1029sub condvar { 1406sub condvar {
1030 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: 1407 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1031} 1408}
1032 1409
1033# default implementation for ->signal 1410# default implementation for ->signal
1034 1411
1035our %SIG_CB; 1412our $HAVE_ASYNC_INTERRUPT;
1413
1414sub _have_async_interrupt() {
1415 $HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
1416 && eval "use Async::Interrupt 1.02 (); 1")
1417 unless defined $HAVE_ASYNC_INTERRUPT;
1418
1419 $HAVE_ASYNC_INTERRUPT
1420}
1421
1422our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
1423our (%SIG_ASY, %SIG_ASY_W);
1424our ($SIG_COUNT, $SIG_TW);
1425
1426sub _signal_exec {
1427 $HAVE_ASYNC_INTERRUPT
1428 ? $SIGPIPE_R->drain
1429 : sysread $SIGPIPE_R, (my $dummy), 9;
1430
1431 while (%SIG_EV) {
1432 for (keys %SIG_EV) {
1433 delete $SIG_EV{$_};
1434 $_->() for values %{ $SIG_CB{$_} || {} };
1435 }
1436 }
1437}
1438
1439# install a dummy wakeup watcher to reduce signal catching latency
1440sub _sig_add() {
1441 unless ($SIG_COUNT++) {
1442 # try to align timer on a full-second boundary, if possible
1443 my $NOW = AE::now;
1444
1445 $SIG_TW = AE::timer
1446 $MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
1447 $MAX_SIGNAL_LATENCY,
1448 sub { } # just for the PERL_ASYNC_CHECK
1449 ;
1450 }
1451}
1452
1453sub _sig_del {
1454 undef $SIG_TW
1455 unless --$SIG_COUNT;
1456}
1457
1458our $_sig_name_init; $_sig_name_init = sub {
1459 eval q{ # poor man's autoloading
1460 undef $_sig_name_init;
1461
1462 if (_have_async_interrupt) {
1463 *sig2num = \&Async::Interrupt::sig2num;
1464 *sig2name = \&Async::Interrupt::sig2name;
1465 } else {
1466 require Config;
1467
1468 my %signame2num;
1469 @signame2num{ split ' ', $Config::Config{sig_name} }
1470 = split ' ', $Config::Config{sig_num};
1471
1472 my @signum2name;
1473 @signum2name[values %signame2num] = keys %signame2num;
1474
1475 *sig2num = sub($) {
1476 $_[0] > 0 ? shift : $signame2num{+shift}
1477 };
1478 *sig2name = sub ($) {
1479 $_[0] > 0 ? $signum2name[+shift] : shift
1480 };
1481 }
1482 };
1483 die if $@;
1484};
1485
1486sub sig2num ($) { &$_sig_name_init; &sig2num }
1487sub sig2name($) { &$_sig_name_init; &sig2name }
1036 1488
1037sub signal { 1489sub signal {
1490 eval q{ # poor man's autoloading {}
1491 # probe for availability of Async::Interrupt
1492 if (_have_async_interrupt) {
1493 warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
1494
1495 $SIGPIPE_R = new Async::Interrupt::EventPipe;
1496 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
1497
1498 } else {
1499 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
1500
1501 require Fcntl;
1502
1503 if (AnyEvent::WIN32) {
1504 require AnyEvent::Util;
1505
1506 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1507 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
1508 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
1509 } else {
1510 pipe $SIGPIPE_R, $SIGPIPE_W;
1511 fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;
1512 fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case
1513
1514 # not strictly required, as $^F is normally 2, but let's make sure...
1515 fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
1516 fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
1517 }
1518
1519 $SIGPIPE_R
1520 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
1521
1522 $SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
1523 }
1524
1525 *signal = sub {
1038 my (undef, %arg) = @_; 1526 my (undef, %arg) = @_;
1039 1527
1040 my $signal = uc $arg{signal} 1528 my $signal = uc $arg{signal}
1041 or Carp::croak "required option 'signal' is missing"; 1529 or Carp::croak "required option 'signal' is missing";
1042 1530
1531 if ($HAVE_ASYNC_INTERRUPT) {
1532 # async::interrupt
1533
1534 $signal = sig2num $signal;
1043 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1535 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1536
1537 $SIG_ASY{$signal} ||= new Async::Interrupt
1538 cb => sub { undef $SIG_EV{$signal} },
1539 signal => $signal,
1540 pipe => [$SIGPIPE_R->filenos],
1541 pipe_autodrain => 0,
1542 ;
1543
1544 } else {
1545 # pure perl
1546
1547 # AE::Util has been loaded in signal
1548 $signal = sig2name $signal;
1549 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1550
1044 $SIG{$signal} ||= sub { 1551 $SIG{$signal} ||= sub {
1045 $_->() for values %{ $SIG_CB{$signal} || {} }; 1552 local $!;
1553 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
1554 undef $SIG_EV{$signal};
1555 };
1556
1557 # can't do signal processing without introducing races in pure perl,
1558 # so limit the signal latency.
1559 _sig_add;
1560 }
1561
1562 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1563 };
1564
1565 *AnyEvent::Base::signal::DESTROY = sub {
1566 my ($signal, $cb) = @{$_[0]};
1567
1568 _sig_del;
1569
1570 delete $SIG_CB{$signal}{$cb};
1571
1572 $HAVE_ASYNC_INTERRUPT
1573 ? delete $SIG_ASY{$signal}
1574 : # delete doesn't work with older perls - they then
1575 # print weird messages, or just unconditionally exit
1576 # instead of getting the default action.
1577 undef $SIG{$signal}
1578 unless keys %{ $SIG_CB{$signal} };
1579 };
1046 }; 1580 };
1047 1581 die if $@;
1048 bless [$signal, $arg{cb}], "AnyEvent::Base::Signal" 1582 &signal
1049}
1050
1051sub AnyEvent::Base::Signal::DESTROY {
1052 my ($signal, $cb) = @{$_[0]};
1053
1054 delete $SIG_CB{$signal}{$cb};
1055
1056 delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1057} 1583}
1058 1584
1059# default implementation for ->child 1585# default implementation for ->child
1060 1586
1061our %PID_CB; 1587our %PID_CB;
1062our $CHLD_W; 1588our $CHLD_W;
1063our $CHLD_DELAY_W; 1589our $CHLD_DELAY_W;
1064our $PID_IDLE;
1065our $WNOHANG; 1590our $WNOHANG;
1066 1591
1067sub _child_wait { 1592sub _emit_childstatus($$) {
1068 while (0 < (my $pid = waitpid -1, $WNOHANG)) { 1593 my (undef, $rpid, $rstatus) = @_;
1594
1595 $_->($rpid, $rstatus)
1069 $_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }), 1596 for values %{ $PID_CB{$rpid} || {} },
1070 (values %{ $PID_CB{0} || {} }); 1597 values %{ $PID_CB{0} || {} };
1071 }
1072
1073 undef $PID_IDLE;
1074} 1598}
1075 1599
1076sub _sigchld { 1600sub _sigchld {
1077 # make sure we deliver these changes "synchronous" with the event loop. 1601 my $pid;
1078 $CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub { 1602
1079 undef $CHLD_DELAY_W; 1603 AnyEvent->_emit_childstatus ($pid, $?)
1080 &_child_wait; 1604 while ($pid = waitpid -1, $WNOHANG) > 0;
1081 });
1082} 1605}
1083 1606
1084sub child { 1607sub child {
1085 my (undef, %arg) = @_; 1608 my (undef, %arg) = @_;
1086 1609
1087 defined (my $pid = $arg{pid} + 0) 1610 defined (my $pid = $arg{pid} + 0)
1088 or Carp::croak "required option 'pid' is missing"; 1611 or Carp::croak "required option 'pid' is missing";
1089 1612
1090 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 1613 $PID_CB{$pid}{$arg{cb}} = $arg{cb};
1091 1614
1092 unless ($WNOHANG) { 1615 # WNOHANG is almost cetrainly 1 everywhere
1616 $WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
1617 ? 1
1093 $WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1; 1618 : eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1094 }
1095 1619
1096 unless ($CHLD_W) { 1620 unless ($CHLD_W) {
1097 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); 1621 $CHLD_W = AE::signal CHLD => \&_sigchld;
1098 # child could be a zombie already, so make at least one round 1622 # child could be a zombie already, so make at least one round
1099 &_sigchld; 1623 &_sigchld;
1100 } 1624 }
1101 1625
1102 bless [$pid, $arg{cb}], "AnyEvent::Base::Child" 1626 bless [$pid, $arg{cb}], "AnyEvent::Base::child"
1103} 1627}
1104 1628
1105sub AnyEvent::Base::Child::DESTROY { 1629sub AnyEvent::Base::child::DESTROY {
1106 my ($pid, $cb) = @{$_[0]}; 1630 my ($pid, $cb) = @{$_[0]};
1107 1631
1108 delete $PID_CB{$pid}{$cb}; 1632 delete $PID_CB{$pid}{$cb};
1109 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 1633 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1110 1634
1111 undef $CHLD_W unless keys %PID_CB; 1635 undef $CHLD_W unless keys %PID_CB;
1112} 1636}
1113 1637
1638# idle emulation is done by simply using a timer, regardless
1639# of whether the process is idle or not, and not letting
1640# the callback use more than 50% of the time.
1641sub idle {
1642 my (undef, %arg) = @_;
1643
1644 my ($cb, $w, $rcb) = $arg{cb};
1645
1646 $rcb = sub {
1647 if ($cb) {
1648 $w = _time;
1649 &$cb;
1650 $w = _time - $w;
1651
1652 # never use more then 50% of the time for the idle watcher,
1653 # within some limits
1654 $w = 0.0001 if $w < 0.0001;
1655 $w = 5 if $w > 5;
1656
1657 $w = AE::timer $w, 0, $rcb;
1658 } else {
1659 # clean up...
1660 undef $w;
1661 undef $rcb;
1662 }
1663 };
1664
1665 $w = AE::timer 0.05, 0, $rcb;
1666
1667 bless \\$cb, "AnyEvent::Base::idle"
1668}
1669
1670sub AnyEvent::Base::idle::DESTROY {
1671 undef $${$_[0]};
1672}
1673
1114package AnyEvent::CondVar; 1674package AnyEvent::CondVar;
1115 1675
1116our @ISA = AnyEvent::CondVar::Base::; 1676our @ISA = AnyEvent::CondVar::Base::;
1117 1677
1118package AnyEvent::CondVar::Base; 1678package AnyEvent::CondVar::Base;
1119 1679
1120use overload 1680#use overload
1121 '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, 1681# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1122 fallback => 1; 1682# fallback => 1;
1683
1684# save 300+ kilobytes by dirtily hardcoding overloading
1685${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
1686*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
1687*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
1688${'AnyEvent::CondVar::Base::()'} = 1; # fallback
1689
1690our $WAITING;
1123 1691
1124sub _send { 1692sub _send {
1125 # nop 1693 # nop
1126} 1694}
1127 1695
1140sub ready { 1708sub ready {
1141 $_[0]{_ae_sent} 1709 $_[0]{_ae_sent}
1142} 1710}
1143 1711
1144sub _wait { 1712sub _wait {
1713 $WAITING
1714 and !$_[0]{_ae_sent}
1715 and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
1716
1717 local $WAITING = 1;
1145 AnyEvent->one_event while !$_[0]{_ae_sent}; 1718 AnyEvent->one_event while !$_[0]{_ae_sent};
1146} 1719}
1147 1720
1148sub recv { 1721sub recv {
1149 $_[0]->_wait; 1722 $_[0]->_wait;
1151 Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; 1724 Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};
1152 wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] 1725 wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]
1153} 1726}
1154 1727
1155sub cb { 1728sub cb {
1156 $_[0]{_ae_cb} = $_[1] if @_ > 1; 1729 my $cv = shift;
1730
1731 @_
1732 and $cv->{_ae_cb} = shift
1733 and $cv->{_ae_sent}
1734 and (delete $cv->{_ae_cb})->($cv);
1735
1157 $_[0]{_ae_cb} 1736 $cv->{_ae_cb}
1158} 1737}
1159 1738
1160sub begin { 1739sub begin {
1161 ++$_[0]{_ae_counter}; 1740 ++$_[0]{_ae_counter};
1162 $_[0]{_ae_end_cb} = $_[1] if @_ > 1; 1741 $_[0]{_ae_end_cb} = $_[1] if @_ > 1;
1168} 1747}
1169 1748
1170# undocumented/compatibility with pre-3.4 1749# undocumented/compatibility with pre-3.4
1171*broadcast = \&send; 1750*broadcast = \&send;
1172*wait = \&_wait; 1751*wait = \&_wait;
1752
1753=head1 ERROR AND EXCEPTION HANDLING
1754
1755In general, AnyEvent does not do any error handling - it relies on the
1756caller to do that if required. The L<AnyEvent::Strict> module (see also
1757the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
1758checking of all AnyEvent methods, however, which is highly useful during
1759development.
1760
1761As for exception handling (i.e. runtime errors and exceptions thrown while
1762executing a callback), this is not only highly event-loop specific, but
1763also not in any way wrapped by this module, as this is the job of the main
1764program.
1765
1766The pure perl event loop simply re-throws the exception (usually
1767within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
1768$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
1769so on.
1770
1771=head1 ENVIRONMENT VARIABLES
1772
1773The following environment variables are used by this module or its
1774submodules.
1775
1776Note that AnyEvent will remove I<all> environment variables starting with
1777C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
1778enabled.
1779
1780=over 4
1781
1782=item C<PERL_ANYEVENT_VERBOSE>
1783
1784By default, AnyEvent will be completely silent except in fatal
1785conditions. You can set this environment variable to make AnyEvent more
1786talkative.
1787
1788When set to C<1> or higher, causes AnyEvent to warn about unexpected
1789conditions, such as not being able to load the event model specified by
1790C<PERL_ANYEVENT_MODEL>.
1791
1792When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1793model it chooses.
1794
1795When set to C<8> or higher, then AnyEvent will report extra information on
1796which optional modules it loads and how it implements certain features.
1797
1798=item C<PERL_ANYEVENT_STRICT>
1799
1800AnyEvent does not do much argument checking by default, as thorough
1801argument checking is very costly. Setting this variable to a true value
1802will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1803check the arguments passed to most method calls. If it finds any problems,
1804it will croak.
1805
1806In other words, enables "strict" mode.
1807
1808Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense>
1809>>, it is definitely recommended to keep it off in production. Keeping
1810C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
1811can be very useful, however.
1812
1813=item C<PERL_ANYEVENT_MODEL>
1814
1815This can be used to specify the event model to be used by AnyEvent, before
1816auto detection and -probing kicks in. It must be a string consisting
1817entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1818and the resulting module name is loaded and if the load was successful,
1819used as event model. If it fails to load AnyEvent will proceed with
1820auto detection and -probing.
1821
1822This functionality might change in future versions.
1823
1824For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1825could start your program like this:
1826
1827 PERL_ANYEVENT_MODEL=Perl perl ...
1828
1829=item C<PERL_ANYEVENT_PROTOCOLS>
1830
1831Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1832for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1833of auto probing).
1834
1835Must be set to a comma-separated list of protocols or address families,
1836current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1837used, and preference will be given to protocols mentioned earlier in the
1838list.
1839
1840This variable can effectively be used for denial-of-service attacks
1841against local programs (e.g. when setuid), although the impact is likely
1842small, as the program has to handle conenction and other failures anyways.
1843
1844Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1845but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1846- only support IPv4, never try to resolve or contact IPv6
1847addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1848IPv6, but prefer IPv6 over IPv4.
1849
1850=item C<PERL_ANYEVENT_EDNS0>
1851
1852Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1853for DNS. This extension is generally useful to reduce DNS traffic, but
1854some (broken) firewalls drop such DNS packets, which is why it is off by
1855default.
1856
1857Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1858EDNS0 in its DNS requests.
1859
1860=item C<PERL_ANYEVENT_MAX_FORKS>
1861
1862The maximum number of child processes that C<AnyEvent::Util::fork_call>
1863will create in parallel.
1864
1865=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
1866
1867The default value for the C<max_outstanding> parameter for the default DNS
1868resolver - this is the maximum number of parallel DNS requests that are
1869sent to the DNS server.
1870
1871=item C<PERL_ANYEVENT_RESOLV_CONF>
1872
1873The file to use instead of F</etc/resolv.conf> (or OS-specific
1874configuration) in the default resolver. When set to the empty string, no
1875default config will be used.
1876
1877=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
1878
1879When neither C<ca_file> nor C<ca_path> was specified during
1880L<AnyEvent::TLS> context creation, and either of these environment
1881variables exist, they will be used to specify CA certificate locations
1882instead of a system-dependent default.
1883
1884=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
1885
1886When these are set to C<1>, then the respective modules are not
1887loaded. Mostly good for testing AnyEvent itself.
1888
1889=back
1173 1890
1174=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 1891=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1175 1892
1176This is an advanced topic that you do not normally need to use AnyEvent in 1893This is an advanced topic that you do not normally need to use AnyEvent in
1177a module. This section is only of use to event loop authors who want to 1894a module. This section is only of use to event loop authors who want to
1211 1928
1212I<rxvt-unicode> also cheats a bit by not providing blocking access to 1929I<rxvt-unicode> also cheats a bit by not providing blocking access to
1213condition variables: code blocking while waiting for a condition will 1930condition variables: code blocking while waiting for a condition will
1214C<die>. This still works with most modules/usages, and blocking calls must 1931C<die>. This still works with most modules/usages, and blocking calls must
1215not be done in an interactive application, so it makes sense. 1932not be done in an interactive application, so it makes sense.
1216
1217=head1 ENVIRONMENT VARIABLES
1218
1219The following environment variables are used by this module:
1220
1221=over 4
1222
1223=item C<PERL_ANYEVENT_VERBOSE>
1224
1225By default, AnyEvent will be completely silent except in fatal
1226conditions. You can set this environment variable to make AnyEvent more
1227talkative.
1228
1229When set to C<1> or higher, causes AnyEvent to warn about unexpected
1230conditions, such as not being able to load the event model specified by
1231C<PERL_ANYEVENT_MODEL>.
1232
1233When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1234model it chooses.
1235
1236=item C<PERL_ANYEVENT_STRICT>
1237
1238AnyEvent does not do much argument checking by default, as thorough
1239argument checking is very costly. Setting this variable to a true value
1240will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1241check the arguments passed to most method calls. If it finds any problems
1242it will croak.
1243
1244In other words, enables "strict" mode.
1245
1246Unlike C<use strict> it is definitely recommended ot keep it off in
1247production.
1248
1249=item C<PERL_ANYEVENT_MODEL>
1250
1251This can be used to specify the event model to be used by AnyEvent, before
1252auto detection and -probing kicks in. It must be a string consisting
1253entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1254and the resulting module name is loaded and if the load was successful,
1255used as event model. If it fails to load AnyEvent will proceed with
1256auto detection and -probing.
1257
1258This functionality might change in future versions.
1259
1260For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1261could start your program like this:
1262
1263 PERL_ANYEVENT_MODEL=Perl perl ...
1264
1265=item C<PERL_ANYEVENT_PROTOCOLS>
1266
1267Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1268for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1269of auto probing).
1270
1271Must be set to a comma-separated list of protocols or address families,
1272current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1273used, and preference will be given to protocols mentioned earlier in the
1274list.
1275
1276This variable can effectively be used for denial-of-service attacks
1277against local programs (e.g. when setuid), although the impact is likely
1278small, as the program has to handle connection errors already-
1279
1280Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1281but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1282- only support IPv4, never try to resolve or contact IPv6
1283addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1284IPv6, but prefer IPv6 over IPv4.
1285
1286=item C<PERL_ANYEVENT_EDNS0>
1287
1288Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1289for DNS. This extension is generally useful to reduce DNS traffic, but
1290some (broken) firewalls drop such DNS packets, which is why it is off by
1291default.
1292
1293Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1294EDNS0 in its DNS requests.
1295
1296=item C<PERL_ANYEVENT_MAX_FORKS>
1297
1298The maximum number of child processes that C<AnyEvent::Util::fork_call>
1299will create in parallel.
1300
1301=back
1302 1933
1303=head1 EXAMPLE PROGRAM 1934=head1 EXAMPLE PROGRAM
1304 1935
1305The following program uses an I/O watcher to read data from STDIN, a timer 1936The following program uses an I/O watcher to read data from STDIN, a timer
1306to display a message once per second, and a condition variable to quit the 1937to display a message once per second, and a condition variable to quit the
1319 warn "read: $input\n"; # output what has been read 1950 warn "read: $input\n"; # output what has been read
1320 $cv->send if $input =~ /^q/i; # quit program if /^q/i 1951 $cv->send if $input =~ /^q/i; # quit program if /^q/i
1321 }, 1952 },
1322 ); 1953 );
1323 1954
1324 my $time_watcher; # can only be used once
1325
1326 sub new_timer {
1327 $timer = AnyEvent->timer (after => 1, cb => sub { 1955 my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1328 warn "timeout\n"; # print 'timeout' about every second 1956 warn "timeout\n"; # print 'timeout' at most every second
1329 &new_timer; # and restart the time
1330 }); 1957 });
1331 }
1332
1333 new_timer; # create first timer
1334 1958
1335 $cv->recv; # wait until user enters /^q/i 1959 $cv->recv; # wait until user enters /^q/i
1336 1960
1337=head1 REAL-WORLD EXAMPLE 1961=head1 REAL-WORLD EXAMPLE
1338 1962
1469through AnyEvent. The benchmark creates a lot of timers (with a zero 2093through AnyEvent. The benchmark creates a lot of timers (with a zero
1470timeout) and I/O watchers (watching STDOUT, a pty, to become writable, 2094timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1471which it is), lets them fire exactly once and destroys them again. 2095which it is), lets them fire exactly once and destroys them again.
1472 2096
1473Source code for this benchmark is found as F<eg/bench> in the AnyEvent 2097Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1474distribution. 2098distribution. It uses the L<AE> interface, which makes a real difference
2099for the EV and Perl backends only.
1475 2100
1476=head3 Explanation of the columns 2101=head3 Explanation of the columns
1477 2102
1478I<watcher> is the number of event watchers created/destroyed. Since 2103I<watcher> is the number of event watchers created/destroyed. Since
1479different event models feature vastly different performances, each event 2104different event models feature vastly different performances, each event
1500watcher. 2125watcher.
1501 2126
1502=head3 Results 2127=head3 Results
1503 2128
1504 name watchers bytes create invoke destroy comment 2129 name watchers bytes create invoke destroy comment
1505 EV/EV 400000 244 0.56 0.46 0.31 EV native interface 2130 EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1506 EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers 2131 EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1507 CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal 2132 Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1508 Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation 2133 Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1509 Event/Event 16000 516 31.88 31.30 0.85 Event native interface 2134 Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1510 Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers 2135 Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
2136 IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
2137 IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1511 Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour 2138 Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1512 Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers 2139 Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1513 POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event 2140 POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1514 POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select 2141 POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1515 2142
1516=head3 Discussion 2143=head3 Discussion
1517 2144
1518The benchmark does I<not> measure scalability of the event loop very 2145The benchmark does I<not> measure scalability of the event loop very
1519well. For example, a select-based event loop (such as the pure perl one) 2146well. For example, a select-based event loop (such as the pure perl one)
1531benchmark machine, handling an event takes roughly 1600 CPU cycles with 2158benchmark machine, handling an event takes roughly 1600 CPU cycles with
1532EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU 2159EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1533cycles with POE. 2160cycles with POE.
1534 2161
1535C<EV> is the sole leader regarding speed and memory use, which are both 2162C<EV> is the sole leader regarding speed and memory use, which are both
1536maximal/minimal, respectively. Even when going through AnyEvent, it uses 2163maximal/minimal, respectively. When using the L<AE> API there is zero
2164overhead (when going through the AnyEvent API create is about 5-6 times
2165slower, with other times being equal, so still uses far less memory than
1537far less memory than any other event loop and is still faster than Event 2166any other event loop and is still faster than Event natively).
1538natively.
1539 2167
1540The pure perl implementation is hit in a few sweet spots (both the 2168The pure perl implementation is hit in a few sweet spots (both the
1541constant timeout and the use of a single fd hit optimisations in the perl 2169constant timeout and the use of a single fd hit optimisations in the perl
1542interpreter and the backend itself). Nevertheless this shows that it 2170interpreter and the backend itself). Nevertheless this shows that it
1543adds very little overhead in itself. Like any select-based backend its 2171adds very little overhead in itself. Like any select-based backend its
1544performance becomes really bad with lots of file descriptors (and few of 2172performance becomes really bad with lots of file descriptors (and few of
1545them active), of course, but this was not subject of this benchmark. 2173them active), of course, but this was not subject of this benchmark.
1546 2174
1547The C<Event> module has a relatively high setup and callback invocation 2175The C<Event> module has a relatively high setup and callback invocation
1548cost, but overall scores in on the third place. 2176cost, but overall scores in on the third place.
2177
2178C<IO::Async> performs admirably well, about on par with C<Event>, even
2179when using its pure perl backend.
1549 2180
1550C<Glib>'s memory usage is quite a bit higher, but it features a 2181C<Glib>'s memory usage is quite a bit higher, but it features a
1551faster callback invocation and overall ends up in the same class as 2182faster callback invocation and overall ends up in the same class as
1552C<Event>. However, Glib scales extremely badly, doubling the number of 2183C<Event>. However, Glib scales extremely badly, doubling the number of
1553watchers increases the processing time by more than a factor of four, 2184watchers increases the processing time by more than a factor of four,
1614In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100 2245In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1615(1%) are active. This mirrors the activity of large servers with many 2246(1%) are active. This mirrors the activity of large servers with many
1616connections, most of which are idle at any one point in time. 2247connections, most of which are idle at any one point in time.
1617 2248
1618Source code for this benchmark is found as F<eg/bench2> in the AnyEvent 2249Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1619distribution. 2250distribution. It uses the L<AE> interface, which makes a real difference
2251for the EV and Perl backends only.
1620 2252
1621=head3 Explanation of the columns 2253=head3 Explanation of the columns
1622 2254
1623I<sockets> is the number of sockets, and twice the number of "servers" (as 2255I<sockets> is the number of sockets, and twice the number of "servers" (as
1624each server has a read and write socket end). 2256each server has a read and write socket end).
1631it to another server. This includes deleting the old timeout and creating 2263it to another server. This includes deleting the old timeout and creating
1632a new one that moves the timeout into the future. 2264a new one that moves the timeout into the future.
1633 2265
1634=head3 Results 2266=head3 Results
1635 2267
1636 name sockets create request 2268 name sockets create request
1637 EV 20000 69.01 11.16 2269 EV 20000 62.66 7.99
1638 Perl 20000 73.32 35.87 2270 Perl 20000 68.32 32.64
1639 Event 20000 212.62 257.32 2271 IOAsync 20000 174.06 101.15 epoll
1640 Glib 20000 651.16 1896.30 2272 IOAsync 20000 174.67 610.84 poll
2273 Event 20000 202.69 242.91
2274 Glib 20000 557.01 1689.52
1641 POE 20000 349.67 12317.24 uses POE::Loop::Event 2275 POE 20000 341.54 12086.32 uses POE::Loop::Event
1642 2276
1643=head3 Discussion 2277=head3 Discussion
1644 2278
1645This benchmark I<does> measure scalability and overall performance of the 2279This benchmark I<does> measure scalability and overall performance of the
1646particular event loop. 2280particular event loop.
1648EV is again fastest. Since it is using epoll on my system, the setup time 2282EV is again fastest. Since it is using epoll on my system, the setup time
1649is relatively high, though. 2283is relatively high, though.
1650 2284
1651Perl surprisingly comes second. It is much faster than the C-based event 2285Perl surprisingly comes second. It is much faster than the C-based event
1652loops Event and Glib. 2286loops Event and Glib.
2287
2288IO::Async performs very well when using its epoll backend, and still quite
2289good compared to Glib when using its pure perl backend.
1653 2290
1654Event suffers from high setup time as well (look at its code and you will 2291Event suffers from high setup time as well (look at its code and you will
1655understand why). Callback invocation also has a high overhead compared to 2292understand why). Callback invocation also has a high overhead compared to
1656the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event 2293the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1657uses select or poll in basically all documented configurations. 2294uses select or poll in basically all documented configurations.
1720=item * C-based event loops perform very well with small number of 2357=item * C-based event loops perform very well with small number of
1721watchers, as the management overhead dominates. 2358watchers, as the management overhead dominates.
1722 2359
1723=back 2360=back
1724 2361
2362=head2 THE IO::Lambda BENCHMARK
2363
2364Recently I was told about the benchmark in the IO::Lambda manpage, which
2365could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
2366simply compares IO::Lambda with POE, and IO::Lambda looks better (which
2367shouldn't come as a surprise to anybody). As such, the benchmark is
2368fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
2369very optimal. But how would AnyEvent compare when used without the extra
2370baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
2371
2372The benchmark itself creates an echo-server, and then, for 500 times,
2373connects to the echo server, sends a line, waits for the reply, and then
2374creates the next connection. This is a rather bad benchmark, as it doesn't
2375test the efficiency of the framework or much non-blocking I/O, but it is a
2376benchmark nevertheless.
2377
2378 name runtime
2379 Lambda/select 0.330 sec
2380 + optimized 0.122 sec
2381 Lambda/AnyEvent 0.327 sec
2382 + optimized 0.138 sec
2383 Raw sockets/select 0.077 sec
2384 POE/select, components 0.662 sec
2385 POE/select, raw sockets 0.226 sec
2386 POE/select, optimized 0.404 sec
2387
2388 AnyEvent/select/nb 0.085 sec
2389 AnyEvent/EV/nb 0.068 sec
2390 +state machine 0.134 sec
2391
2392The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
2393benchmarks actually make blocking connects and use 100% blocking I/O,
2394defeating the purpose of an event-based solution. All of the newly
2395written AnyEvent benchmarks use 100% non-blocking connects (using
2396AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
2397resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
2398generally require a lot more bookkeeping and event handling than blocking
2399connects (which involve a single syscall only).
2400
2401The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
2402offers similar expressive power as POE and IO::Lambda, using conventional
2403Perl syntax. This means that both the echo server and the client are 100%
2404non-blocking, further placing it at a disadvantage.
2405
2406As you can see, the AnyEvent + EV combination even beats the
2407hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
2408backend easily beats IO::Lambda and POE.
2409
2410And even the 100% non-blocking version written using the high-level (and
2411slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
2412higher level ("unoptimised") abstractions by a large margin, even though
2413it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
2414
2415The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
2416F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
2417part of the IO::Lambda distribution and were used without any changes.
2418
2419
2420=head1 SIGNALS
2421
2422AnyEvent currently installs handlers for these signals:
2423
2424=over 4
2425
2426=item SIGCHLD
2427
2428A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
2429emulation for event loops that do not support them natively. Also, some
2430event loops install a similar handler.
2431
2432Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
2433AnyEvent will reset it to default, to avoid losing child exit statuses.
2434
2435=item SIGPIPE
2436
2437A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
2438when AnyEvent gets loaded.
2439
2440The rationale for this is that AnyEvent users usually do not really depend
2441on SIGPIPE delivery (which is purely an optimisation for shell use, or
2442badly-written programs), but C<SIGPIPE> can cause spurious and rare
2443program exits as a lot of people do not expect C<SIGPIPE> when writing to
2444some random socket.
2445
2446The rationale for installing a no-op handler as opposed to ignoring it is
2447that this way, the handler will be restored to defaults on exec.
2448
2449Feel free to install your own handler, or reset it to defaults.
2450
2451=back
2452
2453=cut
2454
2455undef $SIG{CHLD}
2456 if $SIG{CHLD} eq 'IGNORE';
2457
2458$SIG{PIPE} = sub { }
2459 unless defined $SIG{PIPE};
2460
2461=head1 RECOMMENDED/OPTIONAL MODULES
2462
2463One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
2464it's built-in modules) are required to use it.
2465
2466That does not mean that AnyEvent won't take advantage of some additional
2467modules if they are installed.
2468
2469This section explains which additional modules will be used, and how they
2470affect AnyEvent's operation.
2471
2472=over 4
2473
2474=item L<Async::Interrupt>
2475
2476This slightly arcane module is used to implement fast signal handling: To
2477my knowledge, there is no way to do completely race-free and quick
2478signal handling in pure perl. To ensure that signals still get
2479delivered, AnyEvent will start an interval timer to wake up perl (and
2480catch the signals) with some delay (default is 10 seconds, look for
2481C<$AnyEvent::MAX_SIGNAL_LATENCY>).
2482
2483If this module is available, then it will be used to implement signal
2484catching, which means that signals will not be delayed, and the event loop
2485will not be interrupted regularly, which is more efficient (and good for
2486battery life on laptops).
2487
2488This affects not just the pure-perl event loop, but also other event loops
2489that have no signal handling on their own (e.g. Glib, Tk, Qt).
2490
2491Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
2492and either employ their own workarounds (POE) or use AnyEvent's workaround
2493(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
2494does nothing for those backends.
2495
2496=item L<EV>
2497
2498This module isn't really "optional", as it is simply one of the backend
2499event loops that AnyEvent can use. However, it is simply the best event
2500loop available in terms of features, speed and stability: It supports
2501the AnyEvent API optimally, implements all the watcher types in XS, does
2502automatic timer adjustments even when no monotonic clock is available,
2503can take avdantage of advanced kernel interfaces such as C<epoll> and
2504C<kqueue>, and is the fastest backend I<by far>. You can even embed
2505L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
2506
2507=item L<Guard>
2508
2509The guard module, when used, will be used to implement
2510C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
2511lot less memory), but otherwise doesn't affect guard operation much. It is
2512purely used for performance.
2513
2514=item L<JSON> and L<JSON::XS>
2515
2516One of these modules is required when you want to read or write JSON data
2517via L<AnyEvent::Handle>. It is also written in pure-perl, but can take
2518advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
2519
2520In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
2521installed.
2522
2523=item L<Net::SSLeay>
2524
2525Implementing TLS/SSL in Perl is certainly interesting, but not very
2526worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
2527the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
2528
2529=item L<Time::HiRes>
2530
2531This module is part of perl since release 5.008. It will be used when the
2532chosen event library does not come with a timing source on it's own. The
2533pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to
2534try to use a monotonic clock for timing stability.
2535
2536=back
2537
1725 2538
1726=head1 FORK 2539=head1 FORK
1727 2540
1728Most event libraries are not fork-safe. The ones who are usually are 2541Most event libraries are not fork-safe. The ones who are usually are
1729because they rely on inefficient but fork-safe C<select> or C<poll> 2542because they rely on inefficient but fork-safe C<select> or C<poll> calls
1730calls. Only L<EV> is fully fork-aware. 2543- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
2544are usually badly thought-out hacks that are incompatible with fork in
2545one way or another. Only L<EV> is fully fork-aware and ensures that you
2546continue event-processing in both parent and child (or both, if you know
2547what you are doing).
2548
2549This means that, in general, you cannot fork and do event processing in
2550the child if the event library was initialised before the fork (which
2551usually happens when the first AnyEvent watcher is created, or the library
2552is loaded).
1731 2553
1732If you have to fork, you must either do so I<before> creating your first 2554If you have to fork, you must either do so I<before> creating your first
1733watcher OR you must not use AnyEvent at all in the child. 2555watcher OR you must not use AnyEvent at all in the child OR you must do
2556something completely out of the scope of AnyEvent.
2557
2558The problem of doing event processing in the parent I<and> the child
2559is much more complicated: even for backends that I<are> fork-aware or
2560fork-safe, their behaviour is not usually what you want: fork clones all
2561watchers, that means all timers, I/O watchers etc. are active in both
2562parent and child, which is almost never what you want. USing C<exec>
2563to start worker children from some kind of manage rprocess is usually
2564preferred, because it is much easier and cleaner, at the expense of having
2565to have another binary.
1734 2566
1735 2567
1736=head1 SECURITY CONSIDERATIONS 2568=head1 SECURITY CONSIDERATIONS
1737 2569
1738AnyEvent can be forced to load any event model via 2570AnyEvent can be forced to load any event model via
1750 use AnyEvent; 2582 use AnyEvent;
1751 2583
1752Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can 2584Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1753be used to probe what backend is used and gain other information (which is 2585be used to probe what backend is used and gain other information (which is
1754probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and 2586probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1755$ENV{PERL_ANYEGENT_STRICT}. 2587$ENV{PERL_ANYEVENT_STRICT}.
2588
2589Note that AnyEvent will remove I<all> environment variables starting with
2590C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
2591enabled.
1756 2592
1757 2593
1758=head1 BUGS 2594=head1 BUGS
1759 2595
1760Perl 5.8 has numerous memleaks that sometimes hit this module and are hard 2596Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1761to work around. If you suffer from memleaks, first upgrade to Perl 5.10 2597to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1762and check wether the leaks still show up. (Perl 5.10.0 has other annoying 2598and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1763mamleaks, such as leaking on C<map> and C<grep> but it is usually not as 2599memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1764pronounced). 2600pronounced).
1765 2601
1766 2602
1767=head1 SEE ALSO 2603=head1 SEE ALSO
1768 2604
1772L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. 2608L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1773 2609
1774Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, 2610Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1775L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, 2611L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1776L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, 2612L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1777L<AnyEvent::Impl::POE>. 2613L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
1778 2614
1779Non-blocking file handles, sockets, TCP clients and 2615Non-blocking file handles, sockets, TCP clients and
1780servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>. 2616servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1781 2617
1782Asynchronous DNS: L<AnyEvent::DNS>. 2618Asynchronous DNS: L<AnyEvent::DNS>.
1783 2619
1784Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, 2620Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>,
2621L<Coro::Event>,
1785 2622
1786Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. 2623Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>,
2624L<AnyEvent::HTTP>.
1787 2625
1788 2626
1789=head1 AUTHOR 2627=head1 AUTHOR
1790 2628
1791 Marc Lehmann <schmorp@schmorp.de> 2629 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines