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.266 by root, Thu Jul 30 03:41:56 2009 UTC vs.
Revision 1.354 by root, Thu Aug 11 21:26:39 2011 UTC

7 7
8=head1 SYNOPSIS 8=head1 SYNOPSIS
9 9
10 use AnyEvent; 10 use AnyEvent;
11 11
12 # if you prefer function calls, look at the AE manpage for
13 # an alternative API.
14
12 # file descriptor readable 15 # file handle or descriptor readable
13 my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... }); 16 my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
14 17
15 # one-shot or repeating timers 18 # one-shot or repeating timers
16 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... }); 19 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
17 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ... 20 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
18 21
19 print AnyEvent->now; # prints current event loop time 22 print AnyEvent->now; # prints current event loop time
20 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time. 23 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
21 24
22 # POSIX signal 25 # POSIX signal
43in a tutorial or some gentle introduction, have a look at the 46in a tutorial or some gentle introduction, have a look at the
44L<AnyEvent::Intro> manpage. 47L<AnyEvent::Intro> manpage.
45 48
46=head1 SUPPORT 49=head1 SUPPORT
47 50
51An FAQ document is available as L<AnyEvent::FAQ>.
52
48There is a mailinglist for discussing all things AnyEvent, and an IRC 53There also is a mailinglist for discussing all things AnyEvent, and an IRC
49channel, too. 54channel, too.
50 55
51See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software 56See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
52Repository>, at L<http://anyevent.schmorp.de>, for more info. 57Repository>, at L<http://anyevent.schmorp.de>, for more info.
53 58
73module users into the same thing by forcing them to use the same event 78module users into the same thing by forcing them to use the same event
74model you use. 79model you use.
75 80
76For modules like POE or IO::Async (which is a total misnomer as it is 81For modules like POE or IO::Async (which is a total misnomer as it is
77actually doing all I/O I<synchronously>...), using them in your module is 82actually doing all I/O I<synchronously>...), using them in your module is
78like joining a cult: After you joined, you are dependent on them and you 83like joining a cult: After you join, you are dependent on them and you
79cannot use anything else, as they are simply incompatible to everything 84cannot use anything else, as they are simply incompatible to everything
80that isn't them. What's worse, all the potential users of your 85that isn't them. What's worse, all the potential users of your
81module are I<also> forced to use the same event loop you use. 86module are I<also> forced to use the same event loop you use.
82 87
83AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works 88AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
84fine. AnyEvent + Tk works fine etc. etc. but none of these work together 89fine. AnyEvent + Tk works fine etc. etc. but none of these work together
85with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if 90with the rest: POE + EV? No go. Tk + Event? No go. Again: if your module
86your module uses one of those, every user of your module has to use it, 91uses one of those, every user of your module has to use it, too. But if
87too. But if your module uses AnyEvent, it works transparently with all 92your module uses AnyEvent, it works transparently with all event models it
88event models it supports (including stuff like IO::Async, as long as those 93supports (including stuff like IO::Async, as long as those use one of the
89use one of the supported event loops. It is trivial to add new event loops 94supported event loops. It is easy to add new event loops to AnyEvent, too,
90to AnyEvent, too, so it is future-proof). 95so it is future-proof).
91 96
92In addition to being free of having to use I<the one and only true event 97In addition to being free of having to use I<the one and only true event
93model>, AnyEvent also is free of bloat and policy: with POE or similar 98model>, AnyEvent also is free of bloat and policy: with POE or similar
94modules, you get an enormous amount of code and strict rules you have to 99modules, you get an enormous amount of code and strict rules you have to
95follow. AnyEvent, on the other hand, is lean and up to the point, by only 100follow. AnyEvent, on the other hand, is lean and to the point, by only
96offering the functionality that is necessary, in as thin as a wrapper as 101offering the functionality that is necessary, in as thin as a wrapper as
97technically possible. 102technically possible.
98 103
99Of course, AnyEvent comes with a big (and fully optional!) toolbox 104Of course, AnyEvent comes with a big (and fully optional!) toolbox
100of useful functionality, such as an asynchronous DNS resolver, 100% 105of useful functionality, such as an asynchronous DNS resolver, 100%
106useful) and you want to force your users to use the one and only event 111useful) and you want to force your users to use the one and only event
107model, you should I<not> use this module. 112model, you should I<not> use this module.
108 113
109=head1 DESCRIPTION 114=head1 DESCRIPTION
110 115
111L<AnyEvent> provides an identical interface to multiple event loops. This 116L<AnyEvent> provides a uniform interface to various event loops. This
112allows module authors to utilise an event loop without forcing module 117allows module authors to use event loop functionality without forcing
113users to use the same event loop (as only a single event loop can coexist 118module users to use a specific event loop implementation (since more
114peacefully at any one time). 119than one event loop cannot coexist peacefully).
115 120
116The interface itself is vaguely similar, but not identical to the L<Event> 121The interface itself is vaguely similar, but not identical to the L<Event>
117module. 122module.
118 123
119During the first call of any watcher-creation method, the module tries 124During the first call of any watcher-creation method, the module tries
120to detect the currently loaded event loop by probing whether one of the 125to detect the currently loaded event loop by probing whether one of the
121following modules is already loaded: L<EV>, 126following modules is already loaded: L<EV>, L<AnyEvent::Loop>,
122L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>, 127L<Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. The first one
123L<POE>. The first one found is used. If none are found, the module tries 128found is used. If none are detected, the module tries to load the first
124to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl 129four modules in the order given; but note that if L<EV> is not
125adaptor should always succeed) in the order given. The first one that can 130available, the pure-perl L<AnyEvent::Loop> should always work, so
126be successfully loaded will be used. If, after this, still none could be 131the other two are not normally tried.
127found, AnyEvent will fall back to a pure-perl event loop, which is not
128very efficient, but should work everywhere.
129 132
130Because AnyEvent first checks for modules that are already loaded, loading 133Because AnyEvent first checks for modules that are already loaded, loading
131an event model explicitly before first using AnyEvent will likely make 134an event model explicitly before first using AnyEvent will likely make
132that model the default. For example: 135that model the default. For example:
133 136
135 use AnyEvent; 138 use AnyEvent;
136 139
137 # .. AnyEvent will likely default to Tk 140 # .. AnyEvent will likely default to Tk
138 141
139The I<likely> means that, if any module loads another event model and 142The I<likely> means that, if any module loads another event model and
140starts using it, all bets are off. Maybe you should tell their authors to 143starts using it, all bets are off - this case should be very rare though,
141use AnyEvent so their modules work together with others seamlessly... 144as very few modules hardcode event loops without announcing this very
145loudly.
142 146
143The pure-perl implementation of AnyEvent is called 147The pure-perl implementation of AnyEvent is called C<AnyEvent::Loop>. Like
144C<AnyEvent::Impl::Perl>. Like other event modules you can load it 148other event modules you can load it explicitly and enjoy the high
145explicitly and enjoy the high availability of that event loop :) 149availability of that event loop :)
146 150
147=head1 WATCHERS 151=head1 WATCHERS
148 152
149AnyEvent has the central concept of a I<watcher>, which is an object that 153AnyEvent has the central concept of a I<watcher>, which is an object that
150stores relevant data for each kind of event you are waiting for, such as 154stores relevant data for each kind of event you are waiting for, such as
155callback when the event occurs (of course, only when the event model 159callback when the event occurs (of course, only when the event model
156is in control). 160is in control).
157 161
158Note that B<callbacks must not permanently change global variables> 162Note that B<callbacks must not permanently change global variables>
159potentially in use by the event loop (such as C<$_> or C<$[>) and that B<< 163potentially 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 164callbacks must not C<die> >>. The former is good programming practice in
161Perl and the latter stems from the fact that exception handling differs 165Perl and the latter stems from the fact that exception handling differs
162widely between event loops. 166widely between event loops.
163 167
164To disable the watcher you have to destroy it (e.g. by setting the 168To disable a watcher you have to destroy it (e.g. by setting the
165variable you store it in to C<undef> or otherwise deleting all references 169variable you store it in to C<undef> or otherwise deleting all references
166to it). 170to it).
167 171
168All watchers are created by calling a method on the C<AnyEvent> class. 172All watchers are created by calling a method on the C<AnyEvent> class.
169 173
170Many watchers either are used with "recursion" (repeating timers for 174Many watchers either are used with "recursion" (repeating timers for
171example), or need to refer to their watcher object in other ways. 175example), or need to refer to their watcher object in other ways.
172 176
173An any way to achieve that is this pattern: 177One way to achieve that is this pattern:
174 178
175 my $w; $w = AnyEvent->type (arg => value ..., cb => sub { 179 my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
176 # you can use $w here, for example to undef it 180 # you can use $w here, for example to undef it
177 undef $w; 181 undef $w;
178 }); 182 });
210 214
211The I/O watcher might use the underlying file descriptor or a copy of it. 215The I/O watcher might use the underlying file descriptor or a copy of it.
212You must not close a file handle as long as any watcher is active on the 216You must not close a file handle as long as any watcher is active on the
213underlying file descriptor. 217underlying file descriptor.
214 218
215Some event loops issue spurious readyness notifications, so you should 219Some event loops issue spurious readiness notifications, so you should
216always use non-blocking calls when reading/writing from/to your file 220always use non-blocking calls when reading/writing from/to your file
217handles. 221handles.
218 222
219Example: wait for readability of STDIN, then read a line and disable the 223Example: wait for readability of STDIN, then read a line and disable the
220watcher. 224watcher.
244 248
245Although the callback might get passed parameters, their value and 249Although the callback might get passed parameters, their value and
246presence is undefined and you cannot rely on them. Portable AnyEvent 250presence is undefined and you cannot rely on them. Portable AnyEvent
247callbacks cannot use arguments passed to time watcher callbacks. 251callbacks cannot use arguments passed to time watcher callbacks.
248 252
249The callback will normally be invoked once only. If you specify another 253The callback will normally be invoked only once. If you specify another
250parameter, C<interval>, as a strictly positive number (> 0), then the 254parameter, C<interval>, as a strictly positive number (> 0), then the
251callback will be invoked regularly at that interval (in fractional 255callback will be invoked regularly at that interval (in fractional
252seconds) after the first invocation. If C<interval> is specified with a 256seconds) after the first invocation. If C<interval> is specified with a
253false value, then it is treated as if it were missing. 257false value, then it is treated as if it were not specified at all.
254 258
255The callback will be rescheduled before invoking the callback, but no 259The callback will be rescheduled before invoking the callback, but no
256attempt is done to avoid timer drift in most backends, so the interval is 260attempt is made to avoid timer drift in most backends, so the interval is
257only approximate. 261only approximate.
258 262
259Example: fire an event after 7.7 seconds. 263Example: fire an event after 7.7 seconds.
260 264
261 my $w = AnyEvent->timer (after => 7.7, cb => sub { 265 my $w = AnyEvent->timer (after => 7.7, cb => sub {
279 283
280While most event loops expect timers to specified in a relative way, they 284While most event loops expect timers to specified in a relative way, they
281use absolute time internally. This makes a difference when your clock 285use absolute time internally. This makes a difference when your clock
282"jumps", for example, when ntp decides to set your clock backwards from 286"jumps", for example, when ntp decides to set your clock backwards from
283the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to 287the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
284fire "after" a second might actually take six years to finally fire. 288fire "after a second" might actually take six years to finally fire.
285 289
286AnyEvent cannot compensate for this. The only event loop that is conscious 290AnyEvent cannot compensate for this. The only event loop that is conscious
287about these issues is L<EV>, which offers both relative (ev_timer, based 291of these issues is L<EV>, which offers both relative (ev_timer, based
288on true relative time) and absolute (ev_periodic, based on wallclock time) 292on true relative time) and absolute (ev_periodic, based on wallclock time)
289timers. 293timers.
290 294
291AnyEvent always prefers relative timers, if available, matching the 295AnyEvent always prefers relative timers, if available, matching the
292AnyEvent API. 296AnyEvent API.
314I<In almost all cases (in all cases if you don't care), this is the 318I<In almost all cases (in all cases if you don't care), this is the
315function to call when you want to know the current time.> 319function to call when you want to know the current time.>
316 320
317This function is also often faster then C<< AnyEvent->time >>, and 321This function is also often faster then C<< AnyEvent->time >>, and
318thus the preferred method if you want some timestamp (for example, 322thus the preferred method if you want some timestamp (for example,
319L<AnyEvent::Handle> uses this to update it's activity timeouts). 323L<AnyEvent::Handle> uses this to update its activity timeouts).
320 324
321The rest of this section is only of relevance if you try to be very exact 325The rest of this section is only of relevance if you try to be very exact
322with your timing, you can skip it without bad conscience. 326with your timing; you can skip it without a bad conscience.
323 327
324For a practical example of when these times differ, consider L<Event::Lib> 328For a practical example of when these times differ, consider L<Event::Lib>
325and L<EV> and the following set-up: 329and L<EV> and the following set-up:
326 330
327The event loop is running and has just invoked one of your callback at 331The event loop is running and has just invoked one of your callbacks at
328time=500 (assume no other callbacks delay processing). In your callback, 332time=500 (assume no other callbacks delay processing). In your callback,
329you wait a second by executing C<sleep 1> (blocking the process for a 333you wait a second by executing C<sleep 1> (blocking the process for a
330second) and then (at time=501) you create a relative timer that fires 334second) and then (at time=501) you create a relative timer that fires
331after three seconds. 335after three seconds.
332 336
352difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into 356difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
353account. 357account.
354 358
355=item AnyEvent->now_update 359=item AnyEvent->now_update
356 360
357Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache 361Some event loops (such as L<EV> or L<AnyEvent::Loop>) cache the current
358the current time for each loop iteration (see the discussion of L<< 362time for each loop iteration (see the discussion of L<< AnyEvent->now >>,
359AnyEvent->now >>, above). 363above).
360 364
361When a callback runs for a long time (or when the process sleeps), then 365When a callback runs for a long time (or when the process sleeps), then
362this "current" time will differ substantially from the real time, which 366this "current" time will differ substantially from the real time, which
363might affect timers and time-outs. 367might affect timers and time-outs.
364 368
365When this is the case, you can call this method, which will update the 369When this is the case, you can call this method, which will update the
366event loop's idea of "current time". 370event loop's idea of "current time".
371
372A typical example would be a script in a web server (e.g. C<mod_perl>) -
373when mod_perl executes the script, then the event loop will have the wrong
374idea about the "current time" (being potentially far in the past, when the
375script ran the last time). In that case you should arrange a call to C<<
376AnyEvent->now_update >> each time the web server process wakes up again
377(e.g. at the start of your script, or in a handler).
367 378
368Note that updating the time I<might> cause some events to be handled. 379Note that updating the time I<might> cause some events to be handled.
369 380
370=back 381=back
371 382
396 407
397Example: exit on SIGINT 408Example: exit on SIGINT
398 409
399 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); 410 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
400 411
412=head3 Restart Behaviour
413
414While restart behaviour is up to the event loop implementation, most will
415not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's
416pure perl implementation).
417
418=head3 Safe/Unsafe Signals
419
420Perl signals can be either "safe" (synchronous to opcode handling) or
421"unsafe" (asynchronous) - the former might get delayed indefinitely, the
422latter might corrupt your memory.
423
424AnyEvent signal handlers are, in addition, synchronous to the event loop,
425i.e. they will not interrupt your running perl program but will only be
426called as part of the normal event handling (just like timer, I/O etc.
427callbacks, too).
428
401=head3 Signal Races, Delays and Workarounds 429=head3 Signal Races, Delays and Workarounds
402 430
403Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching 431Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
404callbacks to signals in a generic way, which is a pity, as you cannot do 432callbacks to signals in a generic way, which is a pity, as you cannot
405race-free signal handling in perl. AnyEvent will try to do it's best, but 433do race-free signal handling in perl, requiring C libraries for
434this. AnyEvent will try to do its best, which means in some cases,
406in some cases, signals will be delayed. The maximum time a signal might 435signals will be delayed. The maximum time a signal might be delayed is
407be delayed is specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 436specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
408seconds). This variable can be changed only before the first signal 437variable can be changed only before the first signal watcher is created,
409watcher is created, and should be left alone otherwise. Higher values 438and should be left alone otherwise. This variable determines how often
439AnyEvent polls for signals (in case a wake-up was missed). Higher values
410will cause fewer spurious wake-ups, which is better for power and CPU 440will cause fewer spurious wake-ups, which is better for power and CPU
441saving.
442
411saving. All these problems can be avoided by installing the optional 443All these problems can be avoided by installing the optional
412L<Async::Interrupt> module. This will not work with inherently broken 444L<Async::Interrupt> module, which works with most event loops. It will not
413event loops such as L<Event> or L<Event::Lib> (and not with L<POE> 445work with inherently broken event loops such as L<Event> or L<Event::Lib>
414currently, as POE does it's own workaround with one-second latency). With 446(and not with L<POE> currently, as POE does its own workaround with
415those, you just have to suffer the delays. 447one-second latency). For those, you just have to suffer the delays.
416 448
417=head2 CHILD PROCESS WATCHERS 449=head2 CHILD PROCESS WATCHERS
418 450
419 $w = AnyEvent->child (pid => <process id>, cb => <callback>); 451 $w = AnyEvent->child (pid => <process id>, cb => <callback>);
420 452
421You can also watch on a child process exit and catch its exit status. 453You can also watch for a child process exit and catch its exit status.
422 454
423The child process is specified by the C<pid> argument (one some backends, 455The child process is specified by the C<pid> argument (on some backends,
424using C<0> watches for any child process exit, on others this will 456using C<0> watches for any child process exit, on others this will
425croak). The watcher will be triggered only when the child process has 457croak). The watcher will be triggered only when the child process has
426finished and an exit status is available, not on any trace events 458finished and an exit status is available, not on any trace events
427(stopped/continued). 459(stopped/continued).
428 460
450thing in an AnyEvent program, you I<have> to create at least one 482thing in an AnyEvent program, you I<have> to create at least one
451watcher before you C<fork> the child (alternatively, you can call 483watcher before you C<fork> the child (alternatively, you can call
452C<AnyEvent::detect>). 484C<AnyEvent::detect>).
453 485
454As most event loops do not support waiting for child events, they will be 486As most event loops do not support waiting for child events, they will be
455emulated by AnyEvent in most cases, in which the latency and race problems 487emulated by AnyEvent in most cases, in which case the latency and race
456mentioned in the description of signal watchers apply. 488problems mentioned in the description of signal watchers apply.
457 489
458Example: fork a process and wait for it 490Example: fork a process and wait for it
459 491
460 my $done = AnyEvent->condvar; 492 my $done = AnyEvent->condvar;
461 493
475 507
476=head2 IDLE WATCHERS 508=head2 IDLE WATCHERS
477 509
478 $w = AnyEvent->idle (cb => <callback>); 510 $w = AnyEvent->idle (cb => <callback>);
479 511
480Sometimes there is a need to do something, but it is not so important 512This will repeatedly invoke the callback after the process becomes idle,
481to do it instantly, but only when there is nothing better to do. This 513until either the watcher is destroyed or new events have been detected.
482"nothing better to do" is usually defined to be "no other events need
483attention by the event loop".
484 514
485Idle watchers ideally get invoked when the event loop has nothing 515Idle watchers are useful when there is a need to do something, but it
486better to do, just before it would block the process to wait for new 516is not so important (or wise) to do it instantly. The callback will be
487events. Instead of blocking, the idle watcher is invoked. 517invoked only when there is "nothing better to do", which is usually
518defined as "all outstanding events have been handled and no new events
519have been detected". That means that idle watchers ideally get invoked
520when the event loop has just polled for new events but none have been
521detected. Instead of blocking to wait for more events, the idle watchers
522will be invoked.
488 523
489Most event loops unfortunately do not really support idle watchers (only 524Unfortunately, most event loops do not really support idle watchers (only
490EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent 525EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
491will simply call the callback "from time to time". 526will simply call the callback "from time to time".
492 527
493Example: read lines from STDIN, but only process them when the 528Example: read lines from STDIN, but only process them when the
494program is otherwise idle: 529program is otherwise idle:
522will actively watch for new events and call your callbacks. 557will actively watch for new events and call your callbacks.
523 558
524AnyEvent is slightly different: it expects somebody else to run the event 559AnyEvent is slightly different: it expects somebody else to run the event
525loop and will only block when necessary (usually when told by the user). 560loop and will only block when necessary (usually when told by the user).
526 561
527The instrument to do that is called a "condition variable", so called 562The tool to do that is called a "condition variable", so called because
528because they represent a condition that must become true. 563they represent a condition that must become true.
529 564
530Now is probably a good time to look at the examples further below. 565Now is probably a good time to look at the examples further below.
531 566
532Condition variables can be created by calling the C<< AnyEvent->condvar 567Condition variables can be created by calling the C<< AnyEvent->condvar
533>> method, usually without arguments. The only argument pair allowed is 568>> method, usually without arguments. The only argument pair allowed is
538After creation, the condition variable is "false" until it becomes "true" 573After creation, the condition variable is "false" until it becomes "true"
539by calling the C<send> method (or calling the condition variable as if it 574by calling the C<send> method (or calling the condition variable as if it
540were a callback, read about the caveats in the description for the C<< 575were a callback, read about the caveats in the description for the C<<
541->send >> method). 576->send >> method).
542 577
543Condition variables are similar to callbacks, except that you can 578Since condition variables are the most complex part of the AnyEvent API, here are
544optionally wait for them. They can also be called merge points - points 579some different mental models of what they are - pick the ones you can connect to:
545in time where multiple outstanding events have been processed. And yet 580
546another way to call them is transactions - each condition variable can be 581=over 4
547used to represent a transaction, which finishes at some point and delivers 582
548a result. And yet some people know them as "futures" - a promise to 583=item * Condition variables are like callbacks - you can call them (and pass them instead
549compute/deliver something that you can wait for. 584of callbacks). Unlike callbacks however, you can also wait for them to be called.
585
586=item * Condition variables are signals - one side can emit or send them,
587the other side can wait for them, or install a handler that is called when
588the signal fires.
589
590=item * Condition variables are like "Merge Points" - points in your program
591where you merge multiple independent results/control flows into one.
592
593=item * Condition variables represent a transaction - functions that start
594some kind of transaction can return them, leaving the caller the choice
595between waiting in a blocking fashion, or setting a callback.
596
597=item * Condition variables represent future values, or promises to deliver
598some result, long before the result is available.
599
600=back
550 601
551Condition variables are very useful to signal that something has finished, 602Condition variables are very useful to signal that something has finished,
552for example, if you write a module that does asynchronous http requests, 603for example, if you write a module that does asynchronous http requests,
553then a condition variable would be the ideal candidate to signal the 604then a condition variable would be the ideal candidate to signal the
554availability of results. The user can either act when the callback is 605availability of results. The user can either act when the callback is
567 618
568Condition variables are represented by hash refs in perl, and the keys 619Condition variables are represented by hash refs in perl, and the keys
569used by AnyEvent itself are all named C<_ae_XXX> to make subclassing 620used by AnyEvent itself are all named C<_ae_XXX> to make subclassing
570easy (it is often useful to build your own transaction class on top of 621easy (it is often useful to build your own transaction class on top of
571AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call 622AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
572it's C<new> method in your own C<new> method. 623its C<new> method in your own C<new> method.
573 624
574There are two "sides" to a condition variable - the "producer side" which 625There are two "sides" to a condition variable - the "producer side" which
575eventually calls C<< -> send >>, and the "consumer side", which waits 626eventually calls C<< -> send >>, and the "consumer side", which waits
576for the send to occur. 627for the send to occur.
577 628
578Example: wait for a timer. 629Example: wait for a timer.
579 630
580 # wait till the result is ready 631 # condition: "wait till the timer is fired"
581 my $result_ready = AnyEvent->condvar; 632 my $timer_fired = AnyEvent->condvar;
582 633
583 # do something such as adding a timer 634 # create the timer - we could wait for, say
584 # or socket watcher the calls $result_ready->send 635 # a handle becomign ready, or even an
585 # when the "result" is ready. 636 # AnyEvent::HTTP request to finish, but
586 # in this case, we simply use a timer: 637 # in this case, we simply use a timer:
587 my $w = AnyEvent->timer ( 638 my $w = AnyEvent->timer (
588 after => 1, 639 after => 1,
589 cb => sub { $result_ready->send }, 640 cb => sub { $timer_fired->send },
590 ); 641 );
591 642
592 # this "blocks" (while handling events) till the callback 643 # this "blocks" (while handling events) till the callback
593 # calls -<send 644 # calls ->send
594 $result_ready->recv; 645 $timer_fired->recv;
595 646
596Example: wait for a timer, but take advantage of the fact that condition 647Example: wait for a timer, but take advantage of the fact that condition
597variables are also callable directly. 648variables are also callable directly.
598 649
599 my $done = AnyEvent->condvar; 650 my $done = AnyEvent->condvar;
642they were a code reference). Calling them directly is the same as calling 693they were a code reference). Calling them directly is the same as calling
643C<send>. 694C<send>.
644 695
645=item $cv->croak ($error) 696=item $cv->croak ($error)
646 697
647Similar to send, but causes all call's to C<< ->recv >> to invoke 698Similar to send, but causes all calls to C<< ->recv >> to invoke
648C<Carp::croak> with the given error message/object/scalar. 699C<Carp::croak> with the given error message/object/scalar.
649 700
650This can be used to signal any errors to the condition variable 701This can be used to signal any errors to the condition variable
651user/consumer. Doing it this way instead of calling C<croak> directly 702user/consumer. Doing it this way instead of calling C<croak> directly
652delays the error detetcion, but has the overwhelmign advantage that it 703delays the error detection, but has the overwhelming advantage that it
653diagnoses the error at the place where the result is expected, and not 704diagnoses the error at the place where the result is expected, and not
654deep in some event clalback without connection to the actual code causing 705deep in some event callback with no connection to the actual code causing
655the problem. 706the problem.
656 707
657=item $cv->begin ([group callback]) 708=item $cv->begin ([group callback])
658 709
659=item $cv->end 710=item $cv->end
662one. For example, a function that pings many hosts in parallel might want 713one. For example, a function that pings many hosts in parallel might want
663to use a condition variable for the whole process. 714to use a condition variable for the whole process.
664 715
665Every call to C<< ->begin >> will increment a counter, and every call to 716Every call to C<< ->begin >> will increment a counter, and every call to
666C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end 717C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
667>>, the (last) callback passed to C<begin> will be executed. That callback 718>>, the (last) callback passed to C<begin> will be executed, passing the
668is I<supposed> to call C<< ->send >>, but that is not required. If no 719condvar as first argument. That callback is I<supposed> to call C<< ->send
669callback was set, C<send> will be called without any arguments. 720>>, but that is not required. If no group callback was set, C<send> will
721be called without any arguments.
670 722
671You can think of C<< $cv->send >> giving you an OR condition (one call 723You can think of C<< $cv->send >> giving you an OR condition (one call
672sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND 724sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
673condition (all C<begin> calls must be C<end>'ed before the condvar sends). 725condition (all C<begin> calls must be C<end>'ed before the condvar sends).
674 726
696one call to C<begin>, so the condvar waits for all calls to C<end> before 748one call to C<begin>, so the condvar waits for all calls to C<end> before
697sending. 749sending.
698 750
699The ping example mentioned above is slightly more complicated, as the 751The ping example mentioned above is slightly more complicated, as the
700there are results to be passwd back, and the number of tasks that are 752there are results to be passwd back, and the number of tasks that are
701begung can potentially be zero: 753begun can potentially be zero:
702 754
703 my $cv = AnyEvent->condvar; 755 my $cv = AnyEvent->condvar;
704 756
705 my %result; 757 my %result;
706 $cv->begin (sub { $cv->send (\%result) }); 758 $cv->begin (sub { shift->send (\%result) });
707 759
708 for my $host (@list_of_hosts) { 760 for my $host (@list_of_hosts) {
709 $cv->begin; 761 $cv->begin;
710 ping_host_then_call_callback $host, sub { 762 ping_host_then_call_callback $host, sub {
711 $result{$host} = ...; 763 $result{$host} = ...;
727to be called once the counter reaches C<0>, and second, it ensures that 779to be called once the counter reaches C<0>, and second, it ensures that
728C<send> is called even when C<no> hosts are being pinged (the loop 780C<send> is called even when C<no> hosts are being pinged (the loop
729doesn't execute once). 781doesn't execute once).
730 782
731This is the general pattern when you "fan out" into multiple (but 783This is the general pattern when you "fan out" into multiple (but
732potentially none) subrequests: use an outer C<begin>/C<end> pair to set 784potentially zero) subrequests: use an outer C<begin>/C<end> pair to set
733the callback and ensure C<end> is called at least once, and then, for each 785the callback and ensure C<end> is called at least once, and then, for each
734subrequest you start, call C<begin> and for each subrequest you finish, 786subrequest you start, call C<begin> and for each subrequest you finish,
735call C<end>. 787call C<end>.
736 788
737=back 789=back
744=over 4 796=over 4
745 797
746=item $cv->recv 798=item $cv->recv
747 799
748Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak 800Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
749>> methods have been called on c<$cv>, while servicing other watchers 801>> methods have been called on C<$cv>, while servicing other watchers
750normally. 802normally.
751 803
752You can only wait once on a condition - additional calls are valid but 804You can only wait once on a condition - additional calls are valid but
753will return immediately. 805will return immediately.
754 806
771caller decide whether the call will block or not (for example, by coupling 823caller decide whether the call will block or not (for example, by coupling
772condition variables with some kind of request results and supporting 824condition variables with some kind of request results and supporting
773callbacks so the caller knows that getting the result will not block, 825callbacks so the caller knows that getting the result will not block,
774while still supporting blocking waits if the caller so desires). 826while still supporting blocking waits if the caller so desires).
775 827
776You can ensure that C<< -recv >> never blocks by setting a callback and 828You can ensure that C<< ->recv >> never blocks by setting a callback and
777only calling C<< ->recv >> from within that callback (or at a later 829only calling C<< ->recv >> from within that callback (or at a later
778time). This will work even when the event loop does not support blocking 830time). This will work even when the event loop does not support blocking
779waits otherwise. 831waits otherwise.
780 832
781=item $bool = $cv->ready 833=item $bool = $cv->ready
787 839
788This is a mutator function that returns the callback set and optionally 840This is a mutator function that returns the callback set and optionally
789replaces it before doing so. 841replaces it before doing so.
790 842
791The callback will be called when the condition becomes "true", i.e. when 843The callback will be called when the condition becomes "true", i.e. when
792C<send> or C<croak> are called, with the only argument being the condition 844C<send> or C<croak> are called, with the only argument being the
793variable itself. Calling C<recv> inside the callback or at any later time 845condition variable itself. If the condition is already true, the
794is guaranteed not to block. 846callback is called immediately when it is set. Calling C<recv> inside
847the callback or at any later time is guaranteed not to block.
795 848
796=back 849=back
797 850
798=head1 SUPPORTED EVENT LOOPS/BACKENDS 851=head1 SUPPORTED EVENT LOOPS/BACKENDS
799 852
802=over 4 855=over 4
803 856
804=item Backends that are autoprobed when no other event loop can be found. 857=item Backends that are autoprobed when no other event loop can be found.
805 858
806EV is the preferred backend when no other event loop seems to be in 859EV is the preferred backend when no other event loop seems to be in
807use. If EV is not installed, then AnyEvent will try Event, and, failing 860use. If EV is not installed, then AnyEvent will fall back to its own
808that, will fall back to its own pure-perl implementation, which is 861pure-perl implementation, which is available everywhere as it comes with
809available everywhere as it comes with AnyEvent itself. 862AnyEvent itself.
810 863
811 AnyEvent::Impl::EV based on EV (interface to libev, best choice). 864 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
812 AnyEvent::Impl::Event based on Event, very stable, few glitches.
813 AnyEvent::Impl::Perl pure-perl implementation, fast and portable. 865 AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
814 866
815=item Backends that are transparently being picked up when they are used. 867=item Backends that are transparently being picked up when they are used.
816 868
817These will be used when they are currently loaded when the first watcher 869These will be used if they are already loaded when the first watcher
818is created, in which case it is assumed that the application is using 870is created, in which case it is assumed that the application is using
819them. This means that AnyEvent will automatically pick the right backend 871them. This means that AnyEvent will automatically pick the right backend
820when the main program loads an event module before anything starts to 872when the main program loads an event module before anything starts to
821create watchers. Nothing special needs to be done by the main program. 873create watchers. Nothing special needs to be done by the main program.
822 874
875 AnyEvent::Impl::Event based on Event, very stable, few glitches.
823 AnyEvent::Impl::Glib based on Glib, slow but very stable. 876 AnyEvent::Impl::Glib based on Glib, slow but very stable.
824 AnyEvent::Impl::Tk based on Tk, very broken. 877 AnyEvent::Impl::Tk based on Tk, very broken.
825 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 878 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
826 AnyEvent::Impl::POE based on POE, very slow, some limitations. 879 AnyEvent::Impl::POE based on POE, very slow, some limitations.
827 AnyEvent::Impl::Irssi used when running within irssi. 880 AnyEvent::Impl::Irssi used when running within irssi.
881 AnyEvent::Impl::IOAsync based on IO::Async.
882 AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
883 AnyEvent::Impl::FLTK based on FLTK.
828 884
829=item Backends with special needs. 885=item Backends with special needs.
830 886
831Qt requires the Qt::Application to be instantiated first, but will 887Qt requires the Qt::Application to be instantiated first, but will
832otherwise be picked up automatically. As long as the main program 888otherwise be picked up automatically. As long as the main program
833instantiates the application before any AnyEvent watchers are created, 889instantiates the application before any AnyEvent watchers are created,
834everything should just work. 890everything should just work.
835 891
836 AnyEvent::Impl::Qt based on Qt. 892 AnyEvent::Impl::Qt based on Qt.
837 893
838Support for IO::Async can only be partial, as it is too broken and
839architecturally limited to even support the AnyEvent API. It also
840is the only event loop that needs the loop to be set explicitly, so
841it can only be used by a main program knowing about AnyEvent. See
842L<AnyEvent::Impl::Async> for the gory details.
843
844 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
845
846=item Event loops that are indirectly supported via other backends. 894=item Event loops that are indirectly supported via other backends.
847 895
848Some event loops can be supported via other modules: 896Some event loops can be supported via other modules:
849 897
850There is no direct support for WxWidgets (L<Wx>) or L<Prima>. 898There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
875Contains C<undef> until the first watcher is being created, before the 923Contains C<undef> until the first watcher is being created, before the
876backend has been autodetected. 924backend has been autodetected.
877 925
878Afterwards it contains the event model that is being used, which is the 926Afterwards it contains the event model that is being used, which is the
879name of the Perl class implementing the model. This class is usually one 927name of the Perl class implementing the model. This class is usually one
880of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the 928of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
881case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it 929case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
882will be C<urxvt::anyevent>). 930will be C<urxvt::anyevent>).
883 931
884=item AnyEvent::detect 932=item AnyEvent::detect
885 933
886Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 934Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
887if necessary. You should only call this function right before you would 935if necessary. You should only call this function right before you would
888have created an AnyEvent watcher anyway, that is, as late as possible at 936have created an AnyEvent watcher anyway, that is, as late as possible at
889runtime, and not e.g. while initialising of your module. 937runtime, and not e.g. during initialisation of your module.
890 938
891If you need to do some initialisation before AnyEvent watchers are 939If you need to do some initialisation before AnyEvent watchers are
892created, use C<post_detect>. 940created, use C<post_detect>.
893 941
894=item $guard = AnyEvent::post_detect { BLOCK } 942=item $guard = AnyEvent::post_detect { BLOCK }
895 943
896Arranges for the code block to be executed as soon as the event model is 944Arranges for the code block to be executed as soon as the event model is
897autodetected (or immediately if this has already happened). 945autodetected (or immediately if that has already happened).
898 946
899The block will be executed I<after> the actual backend has been detected 947The block will be executed I<after> the actual backend has been detected
900(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been 948(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
901created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do 949created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
902other initialisations - see the sources of L<AnyEvent::Strict> or 950other initialisations - see the sources of L<AnyEvent::Strict> or
911that automatically removes the callback again when it is destroyed (or 959that automatically removes the callback again when it is destroyed (or
912C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for 960C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
913a case where this is useful. 961a case where this is useful.
914 962
915Example: Create a watcher for the IO::AIO module and store it in 963Example: Create a watcher for the IO::AIO module and store it in
916C<$WATCHER>. Only do so after the event loop is initialised, though. 964C<$WATCHER>, but do so only do so after the event loop is initialised.
917 965
918 our WATCHER; 966 our WATCHER;
919 967
920 my $guard = AnyEvent::post_detect { 968 my $guard = AnyEvent::post_detect {
921 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb); 969 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
929 $WATCHER ||= $guard; 977 $WATCHER ||= $guard;
930 978
931=item @AnyEvent::post_detect 979=item @AnyEvent::post_detect
932 980
933If there are any code references in this array (you can C<push> to it 981If there are any code references in this array (you can C<push> to it
934before or after loading AnyEvent), then they will called directly after 982before or after loading AnyEvent), then they will be called directly
935the event loop has been chosen. 983after the event loop has been chosen.
936 984
937You should check C<$AnyEvent::MODEL> before adding to this array, though: 985You should check C<$AnyEvent::MODEL> before adding to this array, though:
938if it is defined then the event loop has already been detected, and the 986if it is defined then the event loop has already been detected, and the
939array will be ignored. 987array will be ignored.
940 988
941Best use C<AnyEvent::post_detect { BLOCK }> when your application allows 989Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
942it,as it takes care of these details. 990it, as it takes care of these details.
943 991
944This variable is mainly useful for modules that can do something useful 992This variable is mainly useful for modules that can do something useful
945when AnyEvent is used and thus want to know when it is initialised, but do 993when AnyEvent is used and thus want to know when it is initialised, but do
946not need to even load it by default. This array provides the means to hook 994not need to even load it by default. This array provides the means to hook
947into AnyEvent passively, without loading it. 995into AnyEvent passively, without loading it.
948 996
997Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
998together, you could put this into Coro (this is the actual code used by
999Coro to accomplish this):
1000
1001 if (defined $AnyEvent::MODEL) {
1002 # AnyEvent already initialised, so load Coro::AnyEvent
1003 require Coro::AnyEvent;
1004 } else {
1005 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
1006 # as soon as it is
1007 push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
1008 }
1009
1010=item AnyEvent::postpone { BLOCK }
1011
1012Arranges for the block to be executed as soon as possible, but not before
1013the call itself returns. In practise, the block will be executed just
1014before the event loop polls for new events, or shortly afterwards.
1015
1016This function never returns anything (to make the C<return postpone { ...
1017}> idiom more useful.
1018
1019To understand the usefulness of this function, consider a function that
1020asynchronously does something for you and returns some transaction
1021object or guard to let you cancel the operation. For example,
1022C<AnyEvent::Socket::tcp_connect>:
1023
1024 # start a conenction attempt unless one is active
1025 $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
1026 delete $self->{connect_guard};
1027 ...
1028 };
1029
1030Imagine that this function could instantly call the callback, for
1031example, because it detects an obvious error such as a negative port
1032number. Invoking the callback before the function returns causes problems
1033however: the callback will be called and will try to delete the guard
1034object. But since the function hasn't returned yet, there is nothing to
1035delete. When the function eventually returns it will assign the guard
1036object to C<< $self->{connect_guard} >>, where it will likely never be
1037deleted, so the program thinks it is still trying to connect.
1038
1039This is where C<AnyEvent::postpone> should be used. Instead of calling the
1040callback directly on error:
1041
1042 $cb->(undef), return # signal error to callback, BAD!
1043 if $some_error_condition;
1044
1045It should use C<postpone>:
1046
1047 AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
1048 if $some_error_condition;
1049
949=back 1050=back
950 1051
951=head1 WHAT TO DO IN A MODULE 1052=head1 WHAT TO DO IN A MODULE
952 1053
953As a module author, you should C<use AnyEvent> and call AnyEvent methods 1054As a module author, you should C<use AnyEvent> and call AnyEvent methods
963because it will stall the whole program, and the whole point of using 1064because it will stall the whole program, and the whole point of using
964events is to stay interactive. 1065events is to stay interactive.
965 1066
966It is fine, however, to call C<< ->recv >> when the user of your module 1067It is fine, however, to call C<< ->recv >> when the user of your module
967requests it (i.e. if you create a http request object ad have a method 1068requests it (i.e. if you create a http request object ad have a method
968called C<results> that returns the results, it should call C<< ->recv >> 1069called C<results> that returns the results, it may call C<< ->recv >>
969freely, as the user of your module knows what she is doing. always). 1070freely, as the user of your module knows what she is doing. Always).
970 1071
971=head1 WHAT TO DO IN THE MAIN PROGRAM 1072=head1 WHAT TO DO IN THE MAIN PROGRAM
972 1073
973There will always be a single main program - the only place that should 1074There will always be a single main program - the only place that should
974dictate which event model to use. 1075dictate which event model to use.
975 1076
976If it doesn't care, it can just "use AnyEvent" and use it itself, or not 1077If the program is not event-based, it need not do anything special, even
977do anything special (it does not need to be event-based) and let AnyEvent 1078when it depends on a module that uses an AnyEvent. If the program itself
978decide which implementation to chose if some module relies on it. 1079uses AnyEvent, but does not care which event loop is used, all it needs
1080to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
1081available loop implementation.
979 1082
980If the main program relies on a specific event model - for example, in 1083If the main program relies on a specific event model - for example, in
981Gtk2 programs you have to rely on the Glib module - you should load the 1084Gtk2 programs you have to rely on the Glib module - you should load the
982event module before loading AnyEvent or any module that uses it: generally 1085event module before loading AnyEvent or any module that uses it: generally
983speaking, you should load it as early as possible. The reason is that 1086speaking, you should load it as early as possible. The reason is that
984modules might create watchers when they are loaded, and AnyEvent will 1087modules might create watchers when they are loaded, and AnyEvent will
985decide on the event model to use as soon as it creates watchers, and it 1088decide on the event model to use as soon as it creates watchers, and it
986might chose the wrong one unless you load the correct one yourself. 1089might choose the wrong one unless you load the correct one yourself.
987 1090
988You can chose to use a pure-perl implementation by loading the 1091You can chose to use a pure-perl implementation by loading the
989C<AnyEvent::Impl::Perl> module, which gives you similar behaviour 1092C<AnyEvent::Loop> module, which gives you similar behaviour
990everywhere, but letting AnyEvent chose the model is generally better. 1093everywhere, but letting AnyEvent chose the model is generally better.
991 1094
992=head2 MAINLOOP EMULATION 1095=head2 MAINLOOP EMULATION
993 1096
994Sometimes (often for short test scripts, or even standalone programs who 1097Sometimes (often for short test scripts, or even standalone programs who
1009=head1 OTHER MODULES 1112=head1 OTHER MODULES
1010 1113
1011The following is a non-exhaustive list of additional modules that use 1114The following is a non-exhaustive list of additional modules that use
1012AnyEvent as a client and can therefore be mixed easily with other AnyEvent 1115AnyEvent as a client and can therefore be mixed easily with other AnyEvent
1013modules and other event loops in the same program. Some of the modules 1116modules and other event loops in the same program. Some of the modules
1014come with AnyEvent, most are available via CPAN. 1117come as part of AnyEvent, the others are available via CPAN.
1015 1118
1016=over 4 1119=over 4
1017 1120
1018=item L<AnyEvent::Util> 1121=item L<AnyEvent::Util>
1019 1122
1020Contains various utility functions that replace often-used but blocking 1123Contains various utility functions that replace often-used blocking
1021functions such as C<inet_aton> by event-/callback-based versions. 1124functions such as C<inet_aton> with event/callback-based versions.
1022 1125
1023=item L<AnyEvent::Socket> 1126=item L<AnyEvent::Socket>
1024 1127
1025Provides various utility functions for (internet protocol) sockets, 1128Provides various utility functions for (internet protocol) sockets,
1026addresses and name resolution. Also functions to create non-blocking tcp 1129addresses and name resolution. Also functions to create non-blocking tcp
1028 1131
1029=item L<AnyEvent::Handle> 1132=item L<AnyEvent::Handle>
1030 1133
1031Provide read and write buffers, manages watchers for reads and writes, 1134Provide read and write buffers, manages watchers for reads and writes,
1032supports raw and formatted I/O, I/O queued and fully transparent and 1135supports raw and formatted I/O, I/O queued and fully transparent and
1033non-blocking SSL/TLS (via L<AnyEvent::TLS>. 1136non-blocking SSL/TLS (via L<AnyEvent::TLS>).
1034 1137
1035=item L<AnyEvent::DNS> 1138=item L<AnyEvent::DNS>
1036 1139
1037Provides rich asynchronous DNS resolver capabilities. 1140Provides rich asynchronous DNS resolver capabilities.
1038 1141
1142=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
1143
1144Implement event-based interfaces to the protocols of the same name (for
1145the curious, IGS is the International Go Server and FCP is the Freenet
1146Client Protocol).
1147
1148=item L<AnyEvent::Handle::UDP>
1149
1150Here be danger!
1151
1152As Pauli would put it, "Not only is it not right, it's not even wrong!" -
1153there are so many things wrong with AnyEvent::Handle::UDP, most notably
1154its use of a stream-based API with a protocol that isn't streamable, that
1155the only way to improve it is to delete it.
1156
1157It features data corruption (but typically only under load) and general
1158confusion. On top, the author is not only clueless about UDP but also
1159fact-resistant - some gems of his understanding: "connect doesn't work
1160with UDP", "UDP packets are not IP packets", "UDP only has datagrams, not
1161packets", "I don't need to implement proper error checking as UDP doesn't
1162support error checking" and so on - he doesn't even understand what's
1163wrong with his module when it is explained to him.
1164
1039=item L<AnyEvent::HTTP> 1165=item L<AnyEvent::DBI>
1040 1166
1041A simple-to-use HTTP library that is capable of making a lot of concurrent 1167Executes L<DBI> requests asynchronously in a proxy process for you,
1042HTTP requests. 1168notifying you in an event-based way when the operation is finished.
1169
1170=item L<AnyEvent::AIO>
1171
1172Truly asynchronous (as opposed to non-blocking) I/O, should be in the
1173toolbox of every event programmer. AnyEvent::AIO transparently fuses
1174L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
1175file I/O, and much more.
1043 1176
1044=item L<AnyEvent::HTTPD> 1177=item L<AnyEvent::HTTPD>
1045 1178
1046Provides a simple web application server framework. 1179A simple embedded webserver.
1047 1180
1048=item L<AnyEvent::FastPing> 1181=item L<AnyEvent::FastPing>
1049 1182
1050The fastest ping in the west. 1183The fastest ping in the west.
1051
1052=item L<AnyEvent::DBI>
1053
1054Executes L<DBI> requests asynchronously in a proxy process.
1055
1056=item L<AnyEvent::AIO>
1057
1058Truly asynchronous I/O, should be in the toolbox of every event
1059programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
1060together.
1061
1062=item L<AnyEvent::BDB>
1063
1064Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
1065L<BDB> and AnyEvent together.
1066
1067=item L<AnyEvent::GPSD>
1068
1069A non-blocking interface to gpsd, a daemon delivering GPS information.
1070
1071=item L<AnyEvent::IRC>
1072
1073AnyEvent based IRC client module family (replacing the older Net::IRC3).
1074
1075=item L<AnyEvent::XMPP>
1076
1077AnyEvent based XMPP (Jabber protocol) module family (replacing the older
1078Net::XMPP2>.
1079
1080=item L<AnyEvent::IGS>
1081
1082A non-blocking interface to the Internet Go Server protocol (used by
1083L<App::IGS>).
1084
1085=item L<Net::FCP>
1086
1087AnyEvent-based implementation of the Freenet Client Protocol, birthplace
1088of AnyEvent.
1089
1090=item L<Event::ExecFlow>
1091
1092High level API for event-based execution flow control.
1093 1184
1094=item L<Coro> 1185=item L<Coro>
1095 1186
1096Has special support for AnyEvent via L<Coro::AnyEvent>. 1187Has special support for AnyEvent via L<Coro::AnyEvent>.
1097 1188
1101 1192
1102package AnyEvent; 1193package AnyEvent;
1103 1194
1104# basically a tuned-down version of common::sense 1195# basically a tuned-down version of common::sense
1105sub common_sense { 1196sub common_sense {
1106 # no warnings 1197 # from common:.sense 3.4
1107 ${^WARNING_BITS} ^= ${^WARNING_BITS}; 1198 ${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
1108 # use strict vars subs 1199 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
1109 $^H |= 0x00000600; 1200 $^H |= 0x00000600;
1110} 1201}
1111 1202
1112BEGIN { AnyEvent::common_sense } 1203BEGIN { AnyEvent::common_sense }
1113 1204
1114use Carp (); 1205use Carp ();
1115 1206
1116our $VERSION = 4.881; 1207our $VERSION = '5.34';
1117our $MODEL; 1208our $MODEL;
1118 1209
1119our $AUTOLOAD; 1210our $AUTOLOAD;
1120our @ISA; 1211our @ISA;
1121 1212
1122our @REGISTRY; 1213our @REGISTRY;
1123 1214
1124our $WIN32;
1125
1126our $VERBOSE; 1215our $VERBOSE;
1127 1216
1128BEGIN { 1217BEGIN {
1129 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }"; 1218 require "AnyEvent/constants.pl";
1219
1130 eval "sub TAINT(){ " . (${^TAINT}*1) . " }"; 1220 eval "sub TAINT (){" . (${^TAINT}*1) . "}";
1131 1221
1132 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV} 1222 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
1133 if ${^TAINT}; 1223 if ${^TAINT};
1134 1224
1135 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1; 1225 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
1147 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; 1237 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
1148} 1238}
1149 1239
1150my @models = ( 1240my @models = (
1151 [EV:: => AnyEvent::Impl::EV:: , 1], 1241 [EV:: => AnyEvent::Impl::EV:: , 1],
1242 [AnyEvent::Loop:: => AnyEvent::Impl::Perl:: , 1],
1243 # everything below here will not (normally) be autoprobed
1244 # as the pure perl backend should work everywhere
1245 # and is usually faster
1152 [Event:: => AnyEvent::Impl::Event::, 1], 1246 [Event:: => AnyEvent::Impl::Event::, 1],
1153 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1],
1154 # everything below here will not (normally) be autoprobed
1155 # as the pureperl backend should work everywhere
1156 # and is usually faster
1157 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers 1247 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
1158 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy 1248 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
1159 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package 1249 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
1160 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles 1250 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
1161 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program 1251 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program
1162 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 1252 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
1163 [Wx:: => AnyEvent::Impl::POE::], 1253 [Wx:: => AnyEvent::Impl::POE::],
1164 [Prima:: => AnyEvent::Impl::POE::], 1254 [Prima:: => AnyEvent::Impl::POE::],
1165 # IO::Async is just too broken - we would need workarounds for its
1166 # byzantine signal and broken child handling, among others.
1167 # IO::Async is rather hard to detect, as it doesn't have any
1168 # obvious default class.
1169# [0, IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
1170# [0, IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program 1255 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::],
1171# [0, IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program 1256 [Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
1257 [FLTK:: => AnyEvent::Impl::FLTK::],
1172); 1258);
1173 1259
1174our %method = map +($_ => 1), 1260our %method = map +($_ => 1),
1175 qw(io timer time now now_update signal child idle condvar one_event DESTROY); 1261 qw(io timer time now now_update signal child idle condvar DESTROY);
1176 1262
1177our @post_detect; 1263our @post_detect;
1178 1264
1179sub post_detect(&) { 1265sub post_detect(&) {
1180 my ($cb) = @_; 1266 my ($cb) = @_;
1181 1267
1182 if ($MODEL) {
1183 $cb->();
1184
1185 undef
1186 } else {
1187 push @post_detect, $cb; 1268 push @post_detect, $cb;
1188 1269
1189 defined wantarray 1270 defined wantarray
1190 ? bless \$cb, "AnyEvent::Util::postdetect" 1271 ? bless \$cb, "AnyEvent::Util::postdetect"
1191 : () 1272 : ()
1192 }
1193} 1273}
1194 1274
1195sub AnyEvent::Util::postdetect::DESTROY { 1275sub AnyEvent::Util::postdetect::DESTROY {
1196 @post_detect = grep $_ != ${$_[0]}, @post_detect; 1276 @post_detect = grep $_ != ${$_[0]}, @post_detect;
1197} 1277}
1198 1278
1199sub detect() { 1279sub detect() {
1280 # free some memory
1281 *detect = sub () { $MODEL };
1282
1283 local $!; # for good measure
1284 local $SIG{__DIE__};
1285
1286 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
1287 my $model = "AnyEvent::Impl::$1";
1288 if (eval "require $model") {
1289 $MODEL = $model;
1290 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
1291 } else {
1292 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
1293 }
1294 }
1295
1296 # check for already loaded models
1200 unless ($MODEL) { 1297 unless ($MODEL) {
1201 local $SIG{__DIE__}; 1298 for (@REGISTRY, @models) {
1202 1299 my ($package, $model) = @$_;
1203 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 1300 if (${"$package\::VERSION"} > 0) {
1204 my $model = "AnyEvent::Impl::$1";
1205 if (eval "require $model") { 1301 if (eval "require $model") {
1206 $MODEL = $model; 1302 $MODEL = $model;
1207 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2; 1303 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
1208 } else { 1304 last;
1209 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE; 1305 }
1210 } 1306 }
1211 } 1307 }
1212 1308
1213 # check for already loaded models
1214 unless ($MODEL) { 1309 unless ($MODEL) {
1310 # try to autoload a model
1215 for (@REGISTRY, @models) { 1311 for (@REGISTRY, @models) {
1216 my ($package, $model) = @$_; 1312 my ($package, $model, $autoload) = @$_;
1313 if (
1314 $autoload
1315 and eval "require $package"
1217 if (${"$package\::VERSION"} > 0) { 1316 and ${"$package\::VERSION"} > 0
1218 if (eval "require $model") { 1317 and eval "require $model"
1318 ) {
1219 $MODEL = $model; 1319 $MODEL = $model;
1220 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2; 1320 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1221 last; 1321 last;
1222 }
1223 } 1322 }
1224 } 1323 }
1225 1324
1226 unless ($MODEL) {
1227 # try to autoload a model
1228 for (@REGISTRY, @models) {
1229 my ($package, $model, $autoload) = @$_;
1230 if (
1231 $autoload
1232 and eval "require $package"
1233 and ${"$package\::VERSION"} > 0
1234 and eval "require $model"
1235 ) {
1236 $MODEL = $model;
1237 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1238 last;
1239 }
1240 }
1241
1242 $MODEL 1325 $MODEL
1243 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n"; 1326 or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?\n";
1244 }
1245 } 1327 }
1246
1247 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1248
1249 unshift @ISA, $MODEL;
1250
1251 require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
1252
1253 (shift @post_detect)->() while @post_detect;
1254 } 1328 }
1329
1330 @models = (); # free probe data
1331
1332 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1333 unshift @ISA, $MODEL;
1334
1335 # now nuke some methods that are overridden by the backend.
1336 # SUPER is not allowed.
1337 for (qw(time signal child idle)) {
1338 undef &{"AnyEvent::Base::$_"}
1339 if defined &{"$MODEL\::$_"};
1340 }
1341
1342 if ($ENV{PERL_ANYEVENT_STRICT}) {
1343 eval { require AnyEvent::Strict };
1344 warn "AnyEvent: cannot load AnyEvent::Strict: $@"
1345 if $@ && $VERBOSE;
1346 }
1347
1348 (shift @post_detect)->() while @post_detect;
1349
1350 *post_detect = sub(&) {
1351 shift->();
1352
1353 undef
1354 };
1255 1355
1256 $MODEL 1356 $MODEL
1257} 1357}
1258 1358
1259sub AUTOLOAD { 1359sub AUTOLOAD {
1260 (my $func = $AUTOLOAD) =~ s/.*://; 1360 (my $func = $AUTOLOAD) =~ s/.*://;
1261 1361
1262 $method{$func} 1362 $method{$func}
1263 or Carp::croak "$func: not a valid method for AnyEvent objects"; 1363 or Carp::croak "$func: not a valid AnyEvent class method";
1264 1364
1265 detect unless $MODEL; 1365 detect;
1266 1366
1267 my $class = shift; 1367 my $class = shift;
1268 $class->$func (@_); 1368 $class->$func (@_);
1369}
1370
1371our $POSTPONE_W;
1372our @POSTPONE;
1373
1374sub _postpone_exec {
1375 undef $POSTPONE_W;
1376 (pop @POSTPONE)->()
1377 while @POSTPONE;
1378}
1379
1380sub postpone(&) {
1381 push @POSTPONE, shift;
1382
1383 $POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
1384
1385 ()
1269} 1386}
1270 1387
1271# utility function to dup a filehandle. this is used by many backends 1388# utility function to dup a filehandle. this is used by many backends
1272# to support binding more than one watcher per filehandle (they usually 1389# to support binding more than one watcher per filehandle (they usually
1273# allow only one watcher per fd, so we dup it to get a different one). 1390# allow only one watcher per fd, so we dup it to get a different one).
1283 # we assume CLOEXEC is already set by perl in all important cases 1400 # we assume CLOEXEC is already set by perl in all important cases
1284 1401
1285 ($fh2, $rw) 1402 ($fh2, $rw)
1286} 1403}
1287 1404
1405=head1 SIMPLIFIED AE API
1406
1407Starting with version 5.0, AnyEvent officially supports a second, much
1408simpler, API that is designed to reduce the calling, typing and memory
1409overhead by using function call syntax and a fixed number of parameters.
1410
1411See the L<AE> manpage for details.
1412
1413=cut
1414
1415package AE;
1416
1417our $VERSION = $AnyEvent::VERSION;
1418
1419# fall back to the main API by default - backends and AnyEvent::Base
1420# implementations can overwrite these.
1421
1422sub io($$$) {
1423 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
1424}
1425
1426sub timer($$$) {
1427 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
1428}
1429
1430sub signal($$) {
1431 AnyEvent->signal (signal => $_[0], cb => $_[1])
1432}
1433
1434sub child($$) {
1435 AnyEvent->child (pid => $_[0], cb => $_[1])
1436}
1437
1438sub idle($) {
1439 AnyEvent->idle (cb => $_[0])
1440}
1441
1442sub cv(;&) {
1443 AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
1444}
1445
1446sub now() {
1447 AnyEvent->now
1448}
1449
1450sub now_update() {
1451 AnyEvent->now_update
1452}
1453
1454sub time() {
1455 AnyEvent->time
1456}
1457
1458*postpone = \&AnyEvent::postpone;
1459
1288package AnyEvent::Base; 1460package AnyEvent::Base;
1289 1461
1290# default implementations for many methods 1462# default implementations for many methods
1291 1463
1292sub _time { 1464sub time {
1465 eval q{ # poor man's autoloading {}
1293 # probe for availability of Time::HiRes 1466 # probe for availability of Time::HiRes
1294 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") { 1467 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
1295 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8; 1468 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
1296 *_time = \&Time::HiRes::time; 1469 *AE::time = \&Time::HiRes::time;
1297 # if (eval "use POSIX (); (POSIX::times())... 1470 # if (eval "use POSIX (); (POSIX::times())...
1298 } else { 1471 } else {
1299 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE; 1472 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
1300 *_time = sub { time }; # epic fail 1473 *AE::time = sub (){ time }; # epic fail
1474 }
1475
1476 *time = sub { AE::time }; # different prototypes
1301 } 1477 };
1478 die if $@;
1302 1479
1303 &_time 1480 &time
1304} 1481}
1305 1482
1306sub time { _time } 1483*now = \&time;
1307sub now { _time } 1484
1308sub now_update { } 1485sub now_update { }
1309 1486
1487sub _poll {
1488 Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
1489}
1490
1310# default implementation for ->condvar 1491# default implementation for ->condvar
1492# in fact, the default should not be overwritten
1311 1493
1312sub condvar { 1494sub condvar {
1495 eval q{ # poor man's autoloading {}
1496 *condvar = sub {
1313 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar" 1497 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1498 };
1499
1500 *AE::cv = sub (;&) {
1501 bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
1502 };
1503 };
1504 die if $@;
1505
1506 &condvar
1314} 1507}
1315 1508
1316# default implementation for ->signal 1509# default implementation for ->signal
1317 1510
1318our $HAVE_ASYNC_INTERRUPT; 1511our $HAVE_ASYNC_INTERRUPT;
1319 1512
1320sub _have_async_interrupt() { 1513sub _have_async_interrupt() {
1321 $HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT} 1514 $HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
1322 && eval "use Async::Interrupt 1.0 (); 1") 1515 && eval "use Async::Interrupt 1.02 (); 1")
1323 unless defined $HAVE_ASYNC_INTERRUPT; 1516 unless defined $HAVE_ASYNC_INTERRUPT;
1324 1517
1325 $HAVE_ASYNC_INTERRUPT 1518 $HAVE_ASYNC_INTERRUPT
1326} 1519}
1327 1520
1328our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO); 1521our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
1329our (%SIG_ASY, %SIG_ASY_W); 1522our (%SIG_ASY, %SIG_ASY_W);
1330our ($SIG_COUNT, $SIG_TW); 1523our ($SIG_COUNT, $SIG_TW);
1331 1524
1332sub _signal_exec {
1333 $HAVE_ASYNC_INTERRUPT
1334 ? $SIGPIPE_R->drain
1335 : sysread $SIGPIPE_R, my $dummy, 9;
1336
1337 while (%SIG_EV) {
1338 for (keys %SIG_EV) {
1339 delete $SIG_EV{$_};
1340 $_->() for values %{ $SIG_CB{$_} || {} };
1341 }
1342 }
1343}
1344
1345# install a dummy wakeup watcher to reduce signal catching latency 1525# install a dummy wakeup watcher to reduce signal catching latency
1526# used by Impls
1346sub _sig_add() { 1527sub _sig_add() {
1347 unless ($SIG_COUNT++) { 1528 unless ($SIG_COUNT++) {
1348 # try to align timer on a full-second boundary, if possible 1529 # try to align timer on a full-second boundary, if possible
1349 my $NOW = AnyEvent->now; 1530 my $NOW = AE::now;
1350 1531
1351 $SIG_TW = AnyEvent->timer ( 1532 $SIG_TW = AE::timer
1352 after => $MAX_SIGNAL_LATENCY - ($NOW - int $NOW), 1533 $MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
1353 interval => $MAX_SIGNAL_LATENCY, 1534 $MAX_SIGNAL_LATENCY,
1354 cb => sub { }, # just for the PERL_ASYNC_CHECK 1535 sub { } # just for the PERL_ASYNC_CHECK
1355 ); 1536 ;
1356 } 1537 }
1357} 1538}
1358 1539
1359sub _sig_del { 1540sub _sig_del {
1360 undef $SIG_TW 1541 undef $SIG_TW
1361 unless --$SIG_COUNT; 1542 unless --$SIG_COUNT;
1362} 1543}
1363 1544
1364our $_sig_name_init; $_sig_name_init = sub { 1545our $_sig_name_init; $_sig_name_init = sub {
1365 eval q{ # poor man's autoloading 1546 eval q{ # poor man's autoloading {}
1366 undef $_sig_name_init; 1547 undef $_sig_name_init;
1367 1548
1368 if (_have_async_interrupt) { 1549 if (_have_async_interrupt) {
1369 *sig2num = \&Async::Interrupt::sig2num; 1550 *sig2num = \&Async::Interrupt::sig2num;
1370 *sig2name = \&Async::Interrupt::sig2name; 1551 *sig2name = \&Async::Interrupt::sig2name;
1397 # probe for availability of Async::Interrupt 1578 # probe for availability of Async::Interrupt
1398 if (_have_async_interrupt) { 1579 if (_have_async_interrupt) {
1399 warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8; 1580 warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
1400 1581
1401 $SIGPIPE_R = new Async::Interrupt::EventPipe; 1582 $SIGPIPE_R = new Async::Interrupt::EventPipe;
1402 $SIG_IO = AnyEvent->io (fh => $SIGPIPE_R->fileno, poll => "r", cb => \&_signal_exec); 1583 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
1403 1584
1404 } else { 1585 } else {
1405 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8; 1586 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
1406
1407 require Fcntl;
1408 1587
1409 if (AnyEvent::WIN32) { 1588 if (AnyEvent::WIN32) {
1410 require AnyEvent::Util; 1589 require AnyEvent::Util;
1411 1590
1412 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe (); 1591 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1413 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R; 1592 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
1414 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case 1593 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
1415 } else { 1594 } else {
1416 pipe $SIGPIPE_R, $SIGPIPE_W; 1595 pipe $SIGPIPE_R, $SIGPIPE_W;
1417 fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R; 1596 fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
1418 fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case 1597 fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
1419 1598
1420 # not strictly required, as $^F is normally 2, but let's make sure... 1599 # not strictly required, as $^F is normally 2, but let's make sure...
1421 fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC; 1600 fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
1422 fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC; 1601 fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
1423 } 1602 }
1424 1603
1425 $SIGPIPE_R 1604 $SIGPIPE_R
1426 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n"; 1605 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
1427 1606
1428 $SIG_IO = AnyEvent->io (fh => $SIGPIPE_R, poll => "r", cb => \&_signal_exec); 1607 $SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
1429 } 1608 }
1430 1609
1431 *signal = sub { 1610 *signal = $HAVE_ASYNC_INTERRUPT
1611 ? sub {
1432 my (undef, %arg) = @_; 1612 my (undef, %arg) = @_;
1433 1613
1434 my $signal = uc $arg{signal}
1435 or Carp::croak "required option 'signal' is missing";
1436
1437 if ($HAVE_ASYNC_INTERRUPT) {
1438 # async::interrupt 1614 # async::interrupt
1439
1440 $signal = sig2num $signal; 1615 my $signal = sig2num $arg{signal};
1441 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1616 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1442 1617
1443 $SIG_ASY{$signal} ||= new Async::Interrupt 1618 $SIG_ASY{$signal} ||= new Async::Interrupt
1444 cb => sub { undef $SIG_EV{$signal} }, 1619 cb => sub { undef $SIG_EV{$signal} },
1445 signal => $signal, 1620 signal => $signal,
1446 pipe => [$SIGPIPE_R->filenos], 1621 pipe => [$SIGPIPE_R->filenos],
1447 pipe_autodrain => 0, 1622 pipe_autodrain => 0,
1448 ; 1623 ;
1449 1624
1450 } else { 1625 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1626 }
1627 : sub {
1628 my (undef, %arg) = @_;
1629
1451 # pure perl 1630 # pure perl
1452
1453 # AE::Util has been loaded in signal
1454 $signal = sig2name $signal; 1631 my $signal = sig2name $arg{signal};
1455 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1632 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1456 1633
1457 $SIG{$signal} ||= sub { 1634 $SIG{$signal} ||= sub {
1458 local $!; 1635 local $!;
1459 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV; 1636 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
1460 undef $SIG_EV{$signal}; 1637 undef $SIG_EV{$signal};
1461 }; 1638 };
1462 1639
1463 # can't do signal processing without introducing races in pure perl, 1640 # can't do signal processing without introducing races in pure perl,
1464 # so limit the signal latency. 1641 # so limit the signal latency.
1465 _sig_add; 1642 _sig_add;
1466 }
1467 1643
1468 bless [$signal, $arg{cb}], "AnyEvent::Base::signal" 1644 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1645 }
1469 }; 1646 ;
1470 1647
1471 *AnyEvent::Base::signal::DESTROY = sub { 1648 *AnyEvent::Base::signal::DESTROY = sub {
1472 my ($signal, $cb) = @{$_[0]}; 1649 my ($signal, $cb) = @{$_[0]};
1473 1650
1474 _sig_del; 1651 _sig_del;
1481 # print weird messages, or just unconditionally exit 1658 # print weird messages, or just unconditionally exit
1482 # instead of getting the default action. 1659 # instead of getting the default action.
1483 undef $SIG{$signal} 1660 undef $SIG{$signal}
1484 unless keys %{ $SIG_CB{$signal} }; 1661 unless keys %{ $SIG_CB{$signal} };
1485 }; 1662 };
1663
1664 *_signal_exec = sub {
1665 $HAVE_ASYNC_INTERRUPT
1666 ? $SIGPIPE_R->drain
1667 : sysread $SIGPIPE_R, (my $dummy), 9;
1668
1669 while (%SIG_EV) {
1670 for (keys %SIG_EV) {
1671 delete $SIG_EV{$_};
1672 $_->() for values %{ $SIG_CB{$_} || {} };
1673 }
1674 }
1675 };
1486 }; 1676 };
1487 die if $@; 1677 die if $@;
1678
1488 &signal 1679 &signal
1489} 1680}
1490 1681
1491# default implementation for ->child 1682# default implementation for ->child
1492 1683
1493our %PID_CB; 1684our %PID_CB;
1494our $CHLD_W; 1685our $CHLD_W;
1495our $CHLD_DELAY_W; 1686our $CHLD_DELAY_W;
1496our $WNOHANG;
1497 1687
1688# used by many Impl's
1498sub _emit_childstatus($$) { 1689sub _emit_childstatus($$) {
1499 my (undef, $rpid, $rstatus) = @_; 1690 my (undef, $rpid, $rstatus) = @_;
1500 1691
1501 $_->($rpid, $rstatus) 1692 $_->($rpid, $rstatus)
1502 for values %{ $PID_CB{$rpid} || {} }, 1693 for values %{ $PID_CB{$rpid} || {} },
1503 values %{ $PID_CB{0} || {} }; 1694 values %{ $PID_CB{0} || {} };
1504} 1695}
1505 1696
1506sub _sigchld {
1507 my $pid;
1508
1509 AnyEvent->_emit_childstatus ($pid, $?)
1510 while ($pid = waitpid -1, $WNOHANG) > 0;
1511}
1512
1513sub child { 1697sub child {
1698 eval q{ # poor man's autoloading {}
1699 *_sigchld = sub {
1700 my $pid;
1701
1702 AnyEvent->_emit_childstatus ($pid, $?)
1703 while ($pid = waitpid -1, WNOHANG) > 0;
1704 };
1705
1706 *child = sub {
1514 my (undef, %arg) = @_; 1707 my (undef, %arg) = @_;
1515 1708
1516 defined (my $pid = $arg{pid} + 0) 1709 my $pid = $arg{pid};
1517 or Carp::croak "required option 'pid' is missing"; 1710 my $cb = $arg{cb};
1518 1711
1519 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 1712 $PID_CB{$pid}{$cb+0} = $cb;
1520 1713
1521 # WNOHANG is almost cetrainly 1 everywhere
1522 $WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
1523 ? 1
1524 : eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1525
1526 unless ($CHLD_W) { 1714 unless ($CHLD_W) {
1527 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); 1715 $CHLD_W = AE::signal CHLD => \&_sigchld;
1528 # child could be a zombie already, so make at least one round 1716 # child could be a zombie already, so make at least one round
1529 &_sigchld; 1717 &_sigchld;
1530 } 1718 }
1531 1719
1532 bless [$pid, $arg{cb}], "AnyEvent::Base::child" 1720 bless [$pid, $cb+0], "AnyEvent::Base::child"
1533} 1721 };
1534 1722
1535sub AnyEvent::Base::child::DESTROY { 1723 *AnyEvent::Base::child::DESTROY = sub {
1536 my ($pid, $cb) = @{$_[0]}; 1724 my ($pid, $icb) = @{$_[0]};
1537 1725
1538 delete $PID_CB{$pid}{$cb}; 1726 delete $PID_CB{$pid}{$icb};
1539 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 1727 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1540 1728
1541 undef $CHLD_W unless keys %PID_CB; 1729 undef $CHLD_W unless keys %PID_CB;
1730 };
1731 };
1732 die if $@;
1733
1734 &child
1542} 1735}
1543 1736
1544# idle emulation is done by simply using a timer, regardless 1737# idle emulation is done by simply using a timer, regardless
1545# of whether the process is idle or not, and not letting 1738# of whether the process is idle or not, and not letting
1546# the callback use more than 50% of the time. 1739# the callback use more than 50% of the time.
1547sub idle { 1740sub idle {
1741 eval q{ # poor man's autoloading {}
1742 *idle = sub {
1548 my (undef, %arg) = @_; 1743 my (undef, %arg) = @_;
1549 1744
1550 my ($cb, $w, $rcb) = $arg{cb}; 1745 my ($cb, $w, $rcb) = $arg{cb};
1551 1746
1552 $rcb = sub { 1747 $rcb = sub {
1553 if ($cb) { 1748 if ($cb) {
1554 $w = _time; 1749 $w = _time;
1555 &$cb; 1750 &$cb;
1556 $w = _time - $w; 1751 $w = _time - $w;
1557 1752
1558 # never use more then 50% of the time for the idle watcher, 1753 # never use more then 50% of the time for the idle watcher,
1559 # within some limits 1754 # within some limits
1560 $w = 0.0001 if $w < 0.0001; 1755 $w = 0.0001 if $w < 0.0001;
1561 $w = 5 if $w > 5; 1756 $w = 5 if $w > 5;
1562 1757
1563 $w = AnyEvent->timer (after => $w, cb => $rcb); 1758 $w = AE::timer $w, 0, $rcb;
1564 } else { 1759 } else {
1565 # clean up... 1760 # clean up...
1566 undef $w; 1761 undef $w;
1567 undef $rcb; 1762 undef $rcb;
1763 }
1764 };
1765
1766 $w = AE::timer 0.05, 0, $rcb;
1767
1768 bless \\$cb, "AnyEvent::Base::idle"
1568 } 1769 };
1770
1771 *AnyEvent::Base::idle::DESTROY = sub {
1772 undef $${$_[0]};
1773 };
1569 }; 1774 };
1775 die if $@;
1570 1776
1571 $w = AnyEvent->timer (after => 0.05, cb => $rcb); 1777 &idle
1572
1573 bless \\$cb, "AnyEvent::Base::idle"
1574}
1575
1576sub AnyEvent::Base::idle::DESTROY {
1577 undef $${$_[0]};
1578} 1778}
1579 1779
1580package AnyEvent::CondVar; 1780package AnyEvent::CondVar;
1581 1781
1582our @ISA = AnyEvent::CondVar::Base::; 1782our @ISA = AnyEvent::CondVar::Base::;
1783
1784# only to be used for subclassing
1785sub new {
1786 my $class = shift;
1787 bless AnyEvent->condvar (@_), $class
1788}
1583 1789
1584package AnyEvent::CondVar::Base; 1790package AnyEvent::CondVar::Base;
1585 1791
1586#use overload 1792#use overload
1587# '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, 1793# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1597 1803
1598sub _send { 1804sub _send {
1599 # nop 1805 # nop
1600} 1806}
1601 1807
1808sub _wait {
1809 AnyEvent->_poll until $_[0]{_ae_sent};
1810}
1811
1602sub send { 1812sub send {
1603 my $cv = shift; 1813 my $cv = shift;
1604 $cv->{_ae_sent} = [@_]; 1814 $cv->{_ae_sent} = [@_];
1605 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb}; 1815 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb};
1606 $cv->_send; 1816 $cv->_send;
1613 1823
1614sub ready { 1824sub ready {
1615 $_[0]{_ae_sent} 1825 $_[0]{_ae_sent}
1616} 1826}
1617 1827
1618sub _wait {
1619 $WAITING
1620 and !$_[0]{_ae_sent}
1621 and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
1622
1623 local $WAITING = 1;
1624 AnyEvent->one_event while !$_[0]{_ae_sent};
1625}
1626
1627sub recv { 1828sub recv {
1829 unless ($_[0]{_ae_sent}) {
1830 $WAITING
1831 and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
1832
1833 local $WAITING = 1;
1628 $_[0]->_wait; 1834 $_[0]->_wait;
1835 }
1629 1836
1630 Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; 1837 $_[0]{_ae_croak}
1631 wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] 1838 and Carp::croak $_[0]{_ae_croak};
1839
1840 wantarray
1841 ? @{ $_[0]{_ae_sent} }
1842 : $_[0]{_ae_sent}[0]
1632} 1843}
1633 1844
1634sub cb { 1845sub cb {
1635 $_[0]{_ae_cb} = $_[1] if @_ > 1; 1846 my $cv = shift;
1847
1848 @_
1849 and $cv->{_ae_cb} = shift
1850 and $cv->{_ae_sent}
1851 and (delete $cv->{_ae_cb})->($cv);
1852
1636 $_[0]{_ae_cb} 1853 $cv->{_ae_cb}
1637} 1854}
1638 1855
1639sub begin { 1856sub begin {
1640 ++$_[0]{_ae_counter}; 1857 ++$_[0]{_ae_counter};
1641 $_[0]{_ae_end_cb} = $_[1] if @_ > 1; 1858 $_[0]{_ae_end_cb} = $_[1] if @_ > 1;
1646 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } }; 1863 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1647} 1864}
1648 1865
1649# undocumented/compatibility with pre-3.4 1866# undocumented/compatibility with pre-3.4
1650*broadcast = \&send; 1867*broadcast = \&send;
1651*wait = \&_wait; 1868*wait = \&recv;
1652
1653#############################################################################
1654# "new" API, currently only emulation of it
1655#############################################################################
1656
1657package AE;
1658
1659sub io($$$) {
1660 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
1661}
1662
1663sub timer($$$) {
1664 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2]);
1665}
1666
1667sub signal($$) {
1668 AnyEvent->signal (signal => $_[0], cb => $_[1]);
1669}
1670
1671sub child($$) {
1672 AnyEvent->child (pid => $_[0], cb => $_[1]);
1673}
1674
1675sub idle($) {
1676 AnyEvent->idle (cb => $_[0]);
1677}
1678
1679sub cv() {
1680 AnyEvent->condvar
1681}
1682
1683sub now() {
1684 AnyEvent->now
1685}
1686
1687sub now_update() {
1688 AnyEvent->now_update
1689}
1690
1691sub time() {
1692 AnyEvent->time
1693}
1694 1869
1695=head1 ERROR AND EXCEPTION HANDLING 1870=head1 ERROR AND EXCEPTION HANDLING
1696 1871
1697In general, AnyEvent does not do any error handling - it relies on the 1872In general, AnyEvent does not do any error handling - it relies on the
1698caller to do that if required. The L<AnyEvent::Strict> module (see also 1873caller to do that if required. The L<AnyEvent::Strict> module (see also
1745check the arguments passed to most method calls. If it finds any problems, 1920check the arguments passed to most method calls. If it finds any problems,
1746it will croak. 1921it will croak.
1747 1922
1748In other words, enables "strict" mode. 1923In other words, enables "strict" mode.
1749 1924
1750Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense> 1925Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
1751>>, it is definitely recommended to keep it off in production. Keeping 1926>>, it is definitely recommended to keep it off in production. Keeping
1752C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs 1927C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
1753can be very useful, however. 1928can be very useful, however.
1754 1929
1755=item C<PERL_ANYEVENT_MODEL> 1930=item C<PERL_ANYEVENT_MODEL>
1761used as event model. If it fails to load AnyEvent will proceed with 1936used as event model. If it fails to load AnyEvent will proceed with
1762auto detection and -probing. 1937auto detection and -probing.
1763 1938
1764This functionality might change in future versions. 1939This functionality might change in future versions.
1765 1940
1766For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you 1941For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
1767could start your program like this: 1942could start your program like this:
1768 1943
1769 PERL_ANYEVENT_MODEL=Perl perl ... 1944 PERL_ANYEVENT_MODEL=Perl perl ...
1770 1945
1771=item C<PERL_ANYEVENT_PROTOCOLS> 1946=item C<PERL_ANYEVENT_PROTOCOLS>
1892 warn "read: $input\n"; # output what has been read 2067 warn "read: $input\n"; # output what has been read
1893 $cv->send if $input =~ /^q/i; # quit program if /^q/i 2068 $cv->send if $input =~ /^q/i; # quit program if /^q/i
1894 }, 2069 },
1895 ); 2070 );
1896 2071
1897 my $time_watcher; # can only be used once
1898
1899 sub new_timer {
1900 $timer = AnyEvent->timer (after => 1, cb => sub { 2072 my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1901 warn "timeout\n"; # print 'timeout' about every second 2073 warn "timeout\n"; # print 'timeout' at most every second
1902 &new_timer; # and restart the time
1903 }); 2074 });
1904 }
1905
1906 new_timer; # create first timer
1907 2075
1908 $cv->recv; # wait until user enters /^q/i 2076 $cv->recv; # wait until user enters /^q/i
1909 2077
1910=head1 REAL-WORLD EXAMPLE 2078=head1 REAL-WORLD EXAMPLE
1911 2079
1984 2152
1985The actual code goes further and collects all errors (C<die>s, exceptions) 2153The actual code goes further and collects all errors (C<die>s, exceptions)
1986that occurred during request processing. The C<result> method detects 2154that occurred during request processing. The C<result> method detects
1987whether an exception as thrown (it is stored inside the $txn object) 2155whether an exception as thrown (it is stored inside the $txn object)
1988and just throws the exception, which means connection errors and other 2156and just throws the exception, which means connection errors and other
1989problems get reported tot he code that tries to use the result, not in a 2157problems get reported to the code that tries to use the result, not in a
1990random callback. 2158random callback.
1991 2159
1992All of this enables the following usage styles: 2160All of this enables the following usage styles:
1993 2161
19941. Blocking: 21621. Blocking:
2042through AnyEvent. The benchmark creates a lot of timers (with a zero 2210through AnyEvent. The benchmark creates a lot of timers (with a zero
2043timeout) and I/O watchers (watching STDOUT, a pty, to become writable, 2211timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
2044which it is), lets them fire exactly once and destroys them again. 2212which it is), lets them fire exactly once and destroys them again.
2045 2213
2046Source code for this benchmark is found as F<eg/bench> in the AnyEvent 2214Source code for this benchmark is found as F<eg/bench> in the AnyEvent
2047distribution. 2215distribution. It uses the L<AE> interface, which makes a real difference
2216for the EV and Perl backends only.
2048 2217
2049=head3 Explanation of the columns 2218=head3 Explanation of the columns
2050 2219
2051I<watcher> is the number of event watchers created/destroyed. Since 2220I<watcher> is the number of event watchers created/destroyed. Since
2052different event models feature vastly different performances, each event 2221different event models feature vastly different performances, each event
2073watcher. 2242watcher.
2074 2243
2075=head3 Results 2244=head3 Results
2076 2245
2077 name watchers bytes create invoke destroy comment 2246 name watchers bytes create invoke destroy comment
2078 EV/EV 400000 224 0.47 0.35 0.27 EV native interface 2247 EV/EV 100000 223 0.47 0.43 0.27 EV native interface
2079 EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers 2248 EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
2080 CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal 2249 Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
2081 Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation 2250 Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
2082 Event/Event 16000 517 32.20 31.80 0.81 Event native interface 2251 Event/Event 16000 516 31.16 31.84 0.82 Event native interface
2083 Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers 2252 Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
2084 IOAsync/Any 16000 989 38.10 32.77 11.13 via IO::Async::Loop::IO_Poll 2253 IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
2085 IOAsync/Any 16000 990 37.59 29.50 10.61 via IO::Async::Loop::Epoll 2254 IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
2086 Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour 2255 Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
2087 Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers 2256 Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
2088 POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event 2257 POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
2089 POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select 2258 POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
2090 2259
2091=head3 Discussion 2260=head3 Discussion
2092 2261
2093The benchmark does I<not> measure scalability of the event loop very 2262The benchmark does I<not> measure scalability of the event loop very
2094well. For example, a select-based event loop (such as the pure perl one) 2263well. For example, a select-based event loop (such as the pure perl one)
2106benchmark machine, handling an event takes roughly 1600 CPU cycles with 2275benchmark machine, handling an event takes roughly 1600 CPU cycles with
2107EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU 2276EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
2108cycles with POE. 2277cycles with POE.
2109 2278
2110C<EV> is the sole leader regarding speed and memory use, which are both 2279C<EV> is the sole leader regarding speed and memory use, which are both
2111maximal/minimal, respectively. Even when going through AnyEvent, it uses 2280maximal/minimal, respectively. When using the L<AE> API there is zero
2281overhead (when going through the AnyEvent API create is about 5-6 times
2282slower, with other times being equal, so still uses far less memory than
2112far less memory than any other event loop and is still faster than Event 2283any other event loop and is still faster than Event natively).
2113natively.
2114 2284
2115The pure perl implementation is hit in a few sweet spots (both the 2285The pure perl implementation is hit in a few sweet spots (both the
2116constant timeout and the use of a single fd hit optimisations in the perl 2286constant timeout and the use of a single fd hit optimisations in the perl
2117interpreter and the backend itself). Nevertheless this shows that it 2287interpreter and the backend itself). Nevertheless this shows that it
2118adds very little overhead in itself. Like any select-based backend its 2288adds very little overhead in itself. Like any select-based backend its
2192In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100 2362In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
2193(1%) are active. This mirrors the activity of large servers with many 2363(1%) are active. This mirrors the activity of large servers with many
2194connections, most of which are idle at any one point in time. 2364connections, most of which are idle at any one point in time.
2195 2365
2196Source code for this benchmark is found as F<eg/bench2> in the AnyEvent 2366Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
2197distribution. 2367distribution. It uses the L<AE> interface, which makes a real difference
2368for the EV and Perl backends only.
2198 2369
2199=head3 Explanation of the columns 2370=head3 Explanation of the columns
2200 2371
2201I<sockets> is the number of sockets, and twice the number of "servers" (as 2372I<sockets> is the number of sockets, and twice the number of "servers" (as
2202each server has a read and write socket end). 2373each server has a read and write socket end).
2210a new one that moves the timeout into the future. 2381a new one that moves the timeout into the future.
2211 2382
2212=head3 Results 2383=head3 Results
2213 2384
2214 name sockets create request 2385 name sockets create request
2215 EV 20000 69.01 11.16 2386 EV 20000 62.66 7.99
2216 Perl 20000 73.32 35.87 2387 Perl 20000 68.32 32.64
2217 IOAsync 20000 157.00 98.14 epoll 2388 IOAsync 20000 174.06 101.15 epoll
2218 IOAsync 20000 159.31 616.06 poll 2389 IOAsync 20000 174.67 610.84 poll
2219 Event 20000 212.62 257.32 2390 Event 20000 202.69 242.91
2220 Glib 20000 651.16 1896.30 2391 Glib 20000 557.01 1689.52
2221 POE 20000 349.67 12317.24 uses POE::Loop::Event 2392 POE 20000 341.54 12086.32 uses POE::Loop::Event
2222 2393
2223=head3 Discussion 2394=head3 Discussion
2224 2395
2225This benchmark I<does> measure scalability and overall performance of the 2396This benchmark I<does> measure scalability and overall performance of the
2226particular event loop. 2397particular event loop.
2352As you can see, the AnyEvent + EV combination even beats the 2523As you can see, the AnyEvent + EV combination even beats the
2353hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl 2524hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
2354backend easily beats IO::Lambda and POE. 2525backend easily beats IO::Lambda and POE.
2355 2526
2356And even the 100% non-blocking version written using the high-level (and 2527And even the 100% non-blocking version written using the high-level (and
2357slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda by a 2528slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
2358large margin, even though it does all of DNS, tcp-connect and socket I/O 2529higher level ("unoptimised") abstractions by a large margin, even though
2359in a non-blocking way. 2530it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
2360 2531
2361The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and 2532The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
2362F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are 2533F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
2363part of the IO::lambda distribution and were used without any changes. 2534part of the IO::Lambda distribution and were used without any changes.
2364 2535
2365 2536
2366=head1 SIGNALS 2537=head1 SIGNALS
2367 2538
2368AnyEvent currently installs handlers for these signals: 2539AnyEvent currently installs handlers for these signals:
2405 unless defined $SIG{PIPE}; 2576 unless defined $SIG{PIPE};
2406 2577
2407=head1 RECOMMENDED/OPTIONAL MODULES 2578=head1 RECOMMENDED/OPTIONAL MODULES
2408 2579
2409One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and 2580One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
2410it's built-in modules) are required to use it. 2581its built-in modules) are required to use it.
2411 2582
2412That does not mean that AnyEvent won't take advantage of some additional 2583That does not mean that AnyEvent won't take advantage of some additional
2413modules if they are installed. 2584modules if they are installed.
2414 2585
2415This section epxlains which additional modules will be used, and how they 2586This section explains which additional modules will be used, and how they
2416affect AnyEvent's operetion. 2587affect AnyEvent's operation.
2417 2588
2418=over 4 2589=over 4
2419 2590
2420=item L<Async::Interrupt> 2591=item L<Async::Interrupt>
2421 2592
2426catch the signals) with some delay (default is 10 seconds, look for 2597catch the signals) with some delay (default is 10 seconds, look for
2427C<$AnyEvent::MAX_SIGNAL_LATENCY>). 2598C<$AnyEvent::MAX_SIGNAL_LATENCY>).
2428 2599
2429If this module is available, then it will be used to implement signal 2600If this module is available, then it will be used to implement signal
2430catching, which means that signals will not be delayed, and the event loop 2601catching, which means that signals will not be delayed, and the event loop
2431will not be interrupted regularly, which is more efficient (And good for 2602will not be interrupted regularly, which is more efficient (and good for
2432battery life on laptops). 2603battery life on laptops).
2433 2604
2434This affects not just the pure-perl event loop, but also other event loops 2605This affects not just the pure-perl event loop, but also other event loops
2435that have no signal handling on their own (e.g. Glib, Tk, Qt). 2606that have no signal handling on their own (e.g. Glib, Tk, Qt).
2436 2607
2448automatic timer adjustments even when no monotonic clock is available, 2619automatic timer adjustments even when no monotonic clock is available,
2449can take avdantage of advanced kernel interfaces such as C<epoll> and 2620can take avdantage of advanced kernel interfaces such as C<epoll> and
2450C<kqueue>, and is the fastest backend I<by far>. You can even embed 2621C<kqueue>, and is the fastest backend I<by far>. You can even embed
2451L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>). 2622L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
2452 2623
2624If you only use backends that rely on another event loop (e.g. C<Tk>),
2625then this module will do nothing for you.
2626
2453=item L<Guard> 2627=item L<Guard>
2454 2628
2455The guard module, when used, will be used to implement 2629The guard module, when used, will be used to implement
2456C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a 2630C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
2457lot less memory), but otherwise doesn't affect guard operation much. It is 2631lot less memory), but otherwise doesn't affect guard operation much. It is
2458purely used for performance. 2632purely used for performance.
2459 2633
2460=item L<JSON> and L<JSON::XS> 2634=item L<JSON> and L<JSON::XS>
2461 2635
2462This module is required when you want to read or write JSON data via 2636One of these modules is required when you want to read or write JSON data
2463L<AnyEvent::Handle>. It is also written in pure-perl, but can take 2637via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
2464advantage of the ultra-high-speed L<JSON::XS> module when it is installed. 2638advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
2465
2466In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
2467installed.
2468 2639
2469=item L<Net::SSLeay> 2640=item L<Net::SSLeay>
2470 2641
2471Implementing TLS/SSL in Perl is certainly interesting, but not very 2642Implementing TLS/SSL in Perl is certainly interesting, but not very
2472worthwhile: If this module is installed, then L<AnyEvent::Handle> (with 2643worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
2473the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL. 2644the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
2474 2645
2475=item L<Time::HiRes> 2646=item L<Time::HiRes>
2476 2647
2477This module is part of perl since release 5.008. It will be used when the 2648This module is part of perl since release 5.008. It will be used when the
2478chosen event library does not come with a timing source on it's own. The 2649chosen event library does not come with a timing source of its own. The
2479pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to 2650pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
2480try to use a monotonic clock for timing stability. 2651try to use a monotonic clock for timing stability.
2481 2652
2482=back 2653=back
2483 2654
2484 2655
2485=head1 FORK 2656=head1 FORK
2486 2657
2487Most event libraries are not fork-safe. The ones who are usually are 2658Most event libraries are not fork-safe. The ones who are usually are
2488because they rely on inefficient but fork-safe C<select> or C<poll> 2659because they rely on inefficient but fork-safe C<select> or C<poll> calls
2489calls. Only L<EV> is fully fork-aware. 2660- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
2661are usually badly thought-out hacks that are incompatible with fork in
2662one way or another. Only L<EV> is fully fork-aware and ensures that you
2663continue event-processing in both parent and child (or both, if you know
2664what you are doing).
2665
2666This means that, in general, you cannot fork and do event processing in
2667the child if the event library was initialised before the fork (which
2668usually happens when the first AnyEvent watcher is created, or the library
2669is loaded).
2490 2670
2491If you have to fork, you must either do so I<before> creating your first 2671If you have to fork, you must either do so I<before> creating your first
2492watcher OR you must not use AnyEvent at all in the child OR you must do 2672watcher OR you must not use AnyEvent at all in the child OR you must do
2493something completely out of the scope of AnyEvent. 2673something completely out of the scope of AnyEvent.
2674
2675The problem of doing event processing in the parent I<and> the child
2676is much more complicated: even for backends that I<are> fork-aware or
2677fork-safe, their behaviour is not usually what you want: fork clones all
2678watchers, that means all timers, I/O watchers etc. are active in both
2679parent and child, which is almost never what you want. USing C<exec>
2680to start worker children from some kind of manage rprocess is usually
2681preferred, because it is much easier and cleaner, at the expense of having
2682to have another binary.
2494 2683
2495 2684
2496=head1 SECURITY CONSIDERATIONS 2685=head1 SECURITY CONSIDERATIONS
2497 2686
2498AnyEvent can be forced to load any event model via 2687AnyEvent can be forced to load any event model via
2528pronounced). 2717pronounced).
2529 2718
2530 2719
2531=head1 SEE ALSO 2720=head1 SEE ALSO
2532 2721
2722Tutorial/Introduction: L<AnyEvent::Intro>.
2723
2724FAQ: L<AnyEvent::FAQ>.
2725
2533Utility functions: L<AnyEvent::Util>. 2726Utility functions: L<AnyEvent::Util>.
2534 2727
2535Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, 2728Event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>, L<Glib::EV>,
2536L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. 2729L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
2537 2730
2538Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, 2731Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
2539L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, 2732L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
2540L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, 2733L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
2541L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>. 2734L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
2543Non-blocking file handles, sockets, TCP clients and 2736Non-blocking file handles, sockets, TCP clients and
2544servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>. 2737servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
2545 2738
2546Asynchronous DNS: L<AnyEvent::DNS>. 2739Asynchronous DNS: L<AnyEvent::DNS>.
2547 2740
2548Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, 2741Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
2549L<Coro::Event>,
2550 2742
2551Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>, 2743Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
2552L<AnyEvent::HTTP>. 2744L<AnyEvent::HTTP>.
2553 2745
2554 2746
2555=head1 AUTHOR 2747=head1 AUTHOR
2556 2748

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines