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.297 by root, Thu Nov 19 01:55:57 2009 UTC vs.
Revision 1.358 by root, Sat Aug 13 02:35:32 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
403 407
404Example: exit on SIGINT 408Example: exit on SIGINT
405 409
406 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); 410 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
407 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
408=head3 Signal Races, Delays and Workarounds 429=head3 Signal Races, Delays and Workarounds
409 430
410Many 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
411callbacks to signals in a generic way, which is a pity, as you cannot 432callbacks to signals in a generic way, which is a pity, as you cannot
412do race-free signal handling in perl, requiring C libraries for 433do race-free signal handling in perl, requiring C libraries for
413this. AnyEvent will try to do it's best, which means in some cases, 434this. AnyEvent will try to do its best, which means in some cases,
414signals will be delayed. The maximum time a signal might be delayed is 435signals will be delayed. The maximum time a signal might be delayed is
415specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This 436specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
416variable can be changed only before the first signal watcher is created, 437variable can be changed only before the first signal watcher is created,
417and should be left alone otherwise. This variable determines how often 438and should be left alone otherwise. This variable determines how often
418AnyEvent polls for signals (in case a wake-up was missed). Higher values 439AnyEvent polls for signals (in case a wake-up was missed). Higher values
420saving. 441saving.
421 442
422All these problems can be avoided by installing the optional 443All these problems can be avoided by installing the optional
423L<Async::Interrupt> module, which works with most event loops. It will not 444L<Async::Interrupt> module, which works with most event loops. It will not
424work with inherently broken event loops such as L<Event> or L<Event::Lib> 445work with inherently broken event loops such as L<Event> or L<Event::Lib>
425(and not with L<POE> currently, as POE does it's own workaround with 446(and not with L<POE> currently, as POE does its own workaround with
426one-second latency). For those, you just have to suffer the delays. 447one-second latency). For those, you just have to suffer the delays.
427 448
428=head2 CHILD PROCESS WATCHERS 449=head2 CHILD PROCESS WATCHERS
429 450
430 $w = AnyEvent->child (pid => <process id>, cb => <callback>); 451 $w = AnyEvent->child (pid => <process id>, cb => <callback>);
431 452
432You 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.
433 454
434The 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,
435using 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
436croak). The watcher will be triggered only when the child process has 457croak). The watcher will be triggered only when the child process has
437finished and an exit status is available, not on any trace events 458finished and an exit status is available, not on any trace events
438(stopped/continued). 459(stopped/continued).
439 460
461thing 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
462watcher before you C<fork> the child (alternatively, you can call 483watcher before you C<fork> the child (alternatively, you can call
463C<AnyEvent::detect>). 484C<AnyEvent::detect>).
464 485
465As 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
466emulated 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
467mentioned in the description of signal watchers apply. 488problems mentioned in the description of signal watchers apply.
468 489
469Example: fork a process and wait for it 490Example: fork a process and wait for it
470 491
471 my $done = AnyEvent->condvar; 492 my $done = AnyEvent->condvar;
472 493
486 507
487=head2 IDLE WATCHERS 508=head2 IDLE WATCHERS
488 509
489 $w = AnyEvent->idle (cb => <callback>); 510 $w = AnyEvent->idle (cb => <callback>);
490 511
491Sometimes there is a need to do something, but it is not so important 512This will repeatedly invoke the callback after the process becomes idle,
492to 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.
493"nothing better to do" is usually defined to be "no other events need
494attention by the event loop".
495 514
496Idle watchers ideally get invoked when the event loop has nothing 515Idle watchers are useful when there is a need to do something, but it
497better 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
498events. 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.
499 523
500Most event loops unfortunately do not really support idle watchers (only 524Unfortunately, most event loops do not really support idle watchers (only
501EV, 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
502will simply call the callback "from time to time". 526will simply call the callback "from time to time".
503 527
504Example: read lines from STDIN, but only process them when the 528Example: read lines from STDIN, but only process them when the
505program is otherwise idle: 529program is otherwise idle:
533will actively watch for new events and call your callbacks. 557will actively watch for new events and call your callbacks.
534 558
535AnyEvent is slightly different: it expects somebody else to run the event 559AnyEvent is slightly different: it expects somebody else to run the event
536loop 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).
537 561
538The instrument to do that is called a "condition variable", so called 562The tool to do that is called a "condition variable", so called because
539because they represent a condition that must become true. 563they represent a condition that must become true.
540 564
541Now 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.
542 566
543Condition variables can be created by calling the C<< AnyEvent->condvar 567Condition variables can be created by calling the C<< AnyEvent->condvar
544>> method, usually without arguments. The only argument pair allowed is 568>> method, usually without arguments. The only argument pair allowed is
549After creation, the condition variable is "false" until it becomes "true" 573After creation, the condition variable is "false" until it becomes "true"
550by 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
551were 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<<
552->send >> method). 576->send >> method).
553 577
554Condition variables are similar to callbacks, except that you can 578Since condition variables are the most complex part of the AnyEvent API, here are
555optionally 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:
556in time where multiple outstanding events have been processed. And yet 580
557another way to call them is transactions - each condition variable can be 581=over 4
558used to represent a transaction, which finishes at some point and delivers 582
559a 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
560compute/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
561 601
562Condition variables are very useful to signal that something has finished, 602Condition variables are very useful to signal that something has finished,
563for example, if you write a module that does asynchronous http requests, 603for example, if you write a module that does asynchronous http requests,
564then a condition variable would be the ideal candidate to signal the 604then a condition variable would be the ideal candidate to signal the
565availability of results. The user can either act when the callback is 605availability of results. The user can either act when the callback is
578 618
579Condition variables are represented by hash refs in perl, and the keys 619Condition variables are represented by hash refs in perl, and the keys
580used 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
581easy (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
582AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call 622AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
583it's C<new> method in your own C<new> method. 623its C<new> method in your own C<new> method.
584 624
585There are two "sides" to a condition variable - the "producer side" which 625There are two "sides" to a condition variable - the "producer side" which
586eventually calls C<< -> send >>, and the "consumer side", which waits 626eventually calls C<< -> send >>, and the "consumer side", which waits
587for the send to occur. 627for the send to occur.
588 628
589Example: wait for a timer. 629Example: wait for a timer.
590 630
591 # wait till the result is ready 631 # condition: "wait till the timer is fired"
592 my $result_ready = AnyEvent->condvar; 632 my $timer_fired = AnyEvent->condvar;
593 633
594 # do something such as adding a timer 634 # create the timer - we could wait for, say
595 # or socket watcher the calls $result_ready->send 635 # a handle becomign ready, or even an
596 # when the "result" is ready. 636 # AnyEvent::HTTP request to finish, but
597 # in this case, we simply use a timer: 637 # in this case, we simply use a timer:
598 my $w = AnyEvent->timer ( 638 my $w = AnyEvent->timer (
599 after => 1, 639 after => 1,
600 cb => sub { $result_ready->send }, 640 cb => sub { $timer_fired->send },
601 ); 641 );
602 642
603 # this "blocks" (while handling events) till the callback 643 # this "blocks" (while handling events) till the callback
604 # calls ->send 644 # calls ->send
605 $result_ready->recv; 645 $timer_fired->recv;
606 646
607Example: 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
608variables are also callable directly. 648variables are also callable directly.
609 649
610 my $done = AnyEvent->condvar; 650 my $done = AnyEvent->condvar;
653they 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
654C<send>. 694C<send>.
655 695
656=item $cv->croak ($error) 696=item $cv->croak ($error)
657 697
658Similar to send, but causes all call's to C<< ->recv >> to invoke 698Similar to send, but causes all calls to C<< ->recv >> to invoke
659C<Carp::croak> with the given error message/object/scalar. 699C<Carp::croak> with the given error message/object/scalar.
660 700
661This can be used to signal any errors to the condition variable 701This can be used to signal any errors to the condition variable
662user/consumer. Doing it this way instead of calling C<croak> directly 702user/consumer. Doing it this way instead of calling C<croak> directly
663delays the error detetcion, but has the overwhelmign advantage that it 703delays the error detection, but has the overwhelming advantage that it
664diagnoses 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
665deep in some event clalback without connection to the actual code causing 705deep in some event callback with no connection to the actual code causing
666the problem. 706the problem.
667 707
668=item $cv->begin ([group callback]) 708=item $cv->begin ([group callback])
669 709
670=item $cv->end 710=item $cv->end
708one 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
709sending. 749sending.
710 750
711The ping example mentioned above is slightly more complicated, as the 751The ping example mentioned above is slightly more complicated, as the
712there 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
713begung can potentially be zero: 753begun can potentially be zero:
714 754
715 my $cv = AnyEvent->condvar; 755 my $cv = AnyEvent->condvar;
716 756
717 my %result; 757 my %result;
718 $cv->begin (sub { shift->send (\%result) }); 758 $cv->begin (sub { shift->send (\%result) });
739to 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
740C<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
741doesn't execute once). 781doesn't execute once).
742 782
743This is the general pattern when you "fan out" into multiple (but 783This is the general pattern when you "fan out" into multiple (but
744potentially 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
745the 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
746subrequest you start, call C<begin> and for each subrequest you finish, 786subrequest you start, call C<begin> and for each subrequest you finish,
747call C<end>. 787call C<end>.
748 788
749=back 789=back
756=over 4 796=over 4
757 797
758=item $cv->recv 798=item $cv->recv
759 799
760Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak 800Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
761>> methods have been called on c<$cv>, while servicing other watchers 801>> methods have been called on C<$cv>, while servicing other watchers
762normally. 802normally.
763 803
764You 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
765will return immediately. 805will return immediately.
766 806
783caller 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
784condition variables with some kind of request results and supporting 824condition variables with some kind of request results and supporting
785callbacks so the caller knows that getting the result will not block, 825callbacks so the caller knows that getting the result will not block,
786while still supporting blocking waits if the caller so desires). 826while still supporting blocking waits if the caller so desires).
787 827
788You 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
789only calling C<< ->recv >> from within that callback (or at a later 829only calling C<< ->recv >> from within that callback (or at a later
790time). 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
791waits otherwise. 831waits otherwise.
792 832
793=item $bool = $cv->ready 833=item $bool = $cv->ready
798=item $cb = $cv->cb ($cb->($cv)) 838=item $cb = $cv->cb ($cb->($cv))
799 839
800This is a mutator function that returns the callback set and optionally 840This is a mutator function that returns the callback set and optionally
801replaces it before doing so. 841replaces it before doing so.
802 842
803The callback will be called when the condition becomes (or already was) 843The callback will be called when the condition becomes "true", i.e. when
804"true", i.e. when C<send> or C<croak> are called (or were called), with 844C<send> or C<croak> are called, with the only argument being the
805the only argument being the condition variable itself. Calling C<recv> 845condition variable itself. If the condition is already true, the
846callback is called immediately when it is set. Calling C<recv> inside
806inside the callback or at any later time is guaranteed not to block. 847the callback or at any later time is guaranteed not to block.
807 848
808=back 849=back
809 850
810=head1 SUPPORTED EVENT LOOPS/BACKENDS 851=head1 SUPPORTED EVENT LOOPS/BACKENDS
811 852
819use. If EV is not installed, then AnyEvent will fall back to its own 860use. If EV is not installed, then AnyEvent will fall back to its own
820pure-perl implementation, which is available everywhere as it comes with 861pure-perl implementation, which is available everywhere as it comes with
821AnyEvent itself. 862AnyEvent itself.
822 863
823 AnyEvent::Impl::EV based on EV (interface to libev, best choice). 864 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
824 AnyEvent::Impl::Perl pure-perl implementation, fast and portable. 865 AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
825 866
826=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.
827 868
828These 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
829is 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
830them. This means that AnyEvent will automatically pick the right backend 871them. This means that AnyEvent will automatically pick the right backend
831when the main program loads an event module before anything starts to 872when the main program loads an event module before anything starts to
832create watchers. Nothing special needs to be done by the main program. 873create watchers. Nothing special needs to be done by the main program.
833 874
835 AnyEvent::Impl::Glib based on Glib, slow but very stable. 876 AnyEvent::Impl::Glib based on Glib, slow but very stable.
836 AnyEvent::Impl::Tk based on Tk, very broken. 877 AnyEvent::Impl::Tk based on Tk, very broken.
837 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 878 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
838 AnyEvent::Impl::POE based on POE, very slow, some limitations. 879 AnyEvent::Impl::POE based on POE, very slow, some limitations.
839 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::FLTK2 based on FLTK (fltk 2 binding).
840 884
841=item Backends with special needs. 885=item Backends with special needs.
842 886
843Qt requires the Qt::Application to be instantiated first, but will 887Qt requires the Qt::Application to be instantiated first, but will
844otherwise be picked up automatically. As long as the main program 888otherwise be picked up automatically. As long as the main program
845instantiates the application before any AnyEvent watchers are created, 889instantiates the application before any AnyEvent watchers are created,
846everything should just work. 890everything should just work.
847 891
848 AnyEvent::Impl::Qt based on Qt. 892 AnyEvent::Impl::Qt based on Qt.
849 893
850Support for IO::Async can only be partial, as it is too broken and
851architecturally limited to even support the AnyEvent API. It also
852is the only event loop that needs the loop to be set explicitly, so
853it can only be used by a main program knowing about AnyEvent. See
854L<AnyEvent::Impl::Async> for the gory details.
855
856 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
857
858=item Event loops that are indirectly supported via other backends. 894=item Event loops that are indirectly supported via other backends.
859 895
860Some event loops can be supported via other modules: 896Some event loops can be supported via other modules:
861 897
862There is no direct support for WxWidgets (L<Wx>) or L<Prima>. 898There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
887Contains C<undef> until the first watcher is being created, before the 923Contains C<undef> until the first watcher is being created, before the
888backend has been autodetected. 924backend has been autodetected.
889 925
890Afterwards 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
891name 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
892of 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
893case 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
894will be C<urxvt::anyevent>). 930will be C<urxvt::anyevent>).
895 931
896=item AnyEvent::detect 932=item AnyEvent::detect
897 933
898Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 934Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
899if necessary. You should only call this function right before you would 935if necessary. You should only call this function right before you would
900have 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
901runtime, and not e.g. while initialising of your module. 937runtime, and not e.g. during initialisation of your module.
902 938
903If you need to do some initialisation before AnyEvent watchers are 939If you need to do some initialisation before AnyEvent watchers are
904created, use C<post_detect>. 940created, use C<post_detect>.
905 941
906=item $guard = AnyEvent::post_detect { BLOCK } 942=item $guard = AnyEvent::post_detect { BLOCK }
907 943
908Arranges 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
909autodetected (or immediately if this has already happened). 945autodetected (or immediately if that has already happened).
910 946
911The 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
912(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
913created, 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
914other initialisations - see the sources of L<AnyEvent::Strict> or 950other initialisations - see the sources of L<AnyEvent::Strict> or
923that automatically removes the callback again when it is destroyed (or 959that automatically removes the callback again when it is destroyed (or
924C<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
925a case where this is useful. 961a case where this is useful.
926 962
927Example: 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
928C<$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.
929 965
930 our WATCHER; 966 our WATCHER;
931 967
932 my $guard = AnyEvent::post_detect { 968 my $guard = AnyEvent::post_detect {
933 $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);
941 $WATCHER ||= $guard; 977 $WATCHER ||= $guard;
942 978
943=item @AnyEvent::post_detect 979=item @AnyEvent::post_detect
944 980
945If 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
946before or after loading AnyEvent), then they will called directly after 982before or after loading AnyEvent), then they will be called directly
947the event loop has been chosen. 983after the event loop has been chosen.
948 984
949You should check C<$AnyEvent::MODEL> before adding to this array, though: 985You should check C<$AnyEvent::MODEL> before adding to this array, though:
950if 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
951array will be ignored. 987array will be ignored.
952 988
953Best use C<AnyEvent::post_detect { BLOCK }> when your application allows 989Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
954it,as it takes care of these details. 990it, as it takes care of these details.
955 991
956This variable is mainly useful for modules that can do something useful 992This variable is mainly useful for modules that can do something useful
957when 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
958not 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
959into AnyEvent passively, without loading it. 995into AnyEvent passively, without loading it.
960 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
961=back 1050=back
962 1051
963=head1 WHAT TO DO IN A MODULE 1052=head1 WHAT TO DO IN A MODULE
964 1053
965As 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
975because 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
976events is to stay interactive. 1065events is to stay interactive.
977 1066
978It 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
979requests 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
980called C<results> that returns the results, it should call C<< ->recv >> 1069called C<results> that returns the results, it may call C<< ->recv >>
981freely, 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).
982 1071
983=head1 WHAT TO DO IN THE MAIN PROGRAM 1072=head1 WHAT TO DO IN THE MAIN PROGRAM
984 1073
985There 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
986dictate which event model to use. 1075dictate which event model to use.
987 1076
988If 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
989do 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
990decide 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.
991 1082
992If 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
993Gtk2 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
994event module before loading AnyEvent or any module that uses it: generally 1085event module before loading AnyEvent or any module that uses it: generally
995speaking, 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
996modules might create watchers when they are loaded, and AnyEvent will 1087modules might create watchers when they are loaded, and AnyEvent will
997decide 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
998might chose the wrong one unless you load the correct one yourself. 1089might choose the wrong one unless you load the correct one yourself.
999 1090
1000You can chose to use a pure-perl implementation by loading the 1091You can chose to use a pure-perl implementation by loading the
1001C<AnyEvent::Impl::Perl> module, which gives you similar behaviour 1092C<AnyEvent::Loop> module, which gives you similar behaviour
1002everywhere, but letting AnyEvent chose the model is generally better. 1093everywhere, but letting AnyEvent chose the model is generally better.
1003 1094
1004=head2 MAINLOOP EMULATION 1095=head2 MAINLOOP EMULATION
1005 1096
1006Sometimes (often for short test scripts, or even standalone programs who 1097Sometimes (often for short test scripts, or even standalone programs who
1021=head1 OTHER MODULES 1112=head1 OTHER MODULES
1022 1113
1023The following is a non-exhaustive list of additional modules that use 1114The following is a non-exhaustive list of additional modules that use
1024AnyEvent 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
1025modules 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
1026come with AnyEvent, most are available via CPAN. 1117come as part of AnyEvent, the others are available via CPAN.
1027 1118
1028=over 4 1119=over 4
1029 1120
1030=item L<AnyEvent::Util> 1121=item L<AnyEvent::Util>
1031 1122
1032Contains various utility functions that replace often-used but blocking 1123Contains various utility functions that replace often-used blocking
1033functions such as C<inet_aton> by event-/callback-based versions. 1124functions such as C<inet_aton> with event/callback-based versions.
1034 1125
1035=item L<AnyEvent::Socket> 1126=item L<AnyEvent::Socket>
1036 1127
1037Provides various utility functions for (internet protocol) sockets, 1128Provides various utility functions for (internet protocol) sockets,
1038addresses and name resolution. Also functions to create non-blocking tcp 1129addresses and name resolution. Also functions to create non-blocking tcp
1040 1131
1041=item L<AnyEvent::Handle> 1132=item L<AnyEvent::Handle>
1042 1133
1043Provide read and write buffers, manages watchers for reads and writes, 1134Provide read and write buffers, manages watchers for reads and writes,
1044supports 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
1045non-blocking SSL/TLS (via L<AnyEvent::TLS>. 1136non-blocking SSL/TLS (via L<AnyEvent::TLS>).
1046 1137
1047=item L<AnyEvent::DNS> 1138=item L<AnyEvent::DNS>
1048 1139
1049Provides rich asynchronous DNS resolver capabilities. 1140Provides rich asynchronous DNS resolver capabilities.
1050 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
1051=item L<AnyEvent::HTTP> 1165=item L<AnyEvent::DBI>
1052 1166
1053A 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,
1054HTTP 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.
1055 1176
1056=item L<AnyEvent::HTTPD> 1177=item L<AnyEvent::HTTPD>
1057 1178
1058Provides a simple web application server framework. 1179A simple embedded webserver.
1059 1180
1060=item L<AnyEvent::FastPing> 1181=item L<AnyEvent::FastPing>
1061 1182
1062The fastest ping in the west. 1183The fastest ping in the west.
1063
1064=item L<AnyEvent::DBI>
1065
1066Executes L<DBI> requests asynchronously in a proxy process.
1067
1068=item L<AnyEvent::AIO>
1069
1070Truly asynchronous I/O, should be in the toolbox of every event
1071programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
1072together.
1073
1074=item L<AnyEvent::BDB>
1075
1076Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
1077L<BDB> and AnyEvent together.
1078
1079=item L<AnyEvent::GPSD>
1080
1081A non-blocking interface to gpsd, a daemon delivering GPS information.
1082
1083=item L<AnyEvent::IRC>
1084
1085AnyEvent based IRC client module family (replacing the older Net::IRC3).
1086
1087=item L<AnyEvent::XMPP>
1088
1089AnyEvent based XMPP (Jabber protocol) module family (replacing the older
1090Net::XMPP2>.
1091
1092=item L<AnyEvent::IGS>
1093
1094A non-blocking interface to the Internet Go Server protocol (used by
1095L<App::IGS>).
1096
1097=item L<Net::FCP>
1098
1099AnyEvent-based implementation of the Freenet Client Protocol, birthplace
1100of AnyEvent.
1101
1102=item L<Event::ExecFlow>
1103
1104High level API for event-based execution flow control.
1105 1184
1106=item L<Coro> 1185=item L<Coro>
1107 1186
1108Has special support for AnyEvent via L<Coro::AnyEvent>. 1187Has special support for AnyEvent via L<Coro::AnyEvent>.
1109 1188
1113 1192
1114package AnyEvent; 1193package AnyEvent;
1115 1194
1116# basically a tuned-down version of common::sense 1195# basically a tuned-down version of common::sense
1117sub common_sense { 1196sub common_sense {
1118 # from common:.sense 1.0 1197 # from common:.sense 3.4
1119 ${^WARNING_BITS} = "\xfc\x3f\xf3\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x03"; 1198 ${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
1120 # use strict vars subs 1199 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
1121 $^H |= 0x00000600; 1200 $^H |= 0x00000600;
1122} 1201}
1123 1202
1124BEGIN { AnyEvent::common_sense } 1203BEGIN { AnyEvent::common_sense }
1125 1204
1126use Carp (); 1205use Carp ();
1127 1206
1128our $VERSION = '5.21'; 1207our $VERSION = '5.34';
1129our $MODEL; 1208our $MODEL;
1130 1209
1131our $AUTOLOAD;
1132our @ISA; 1210our @ISA;
1133 1211
1134our @REGISTRY; 1212our @REGISTRY;
1135 1213
1136our $VERBOSE; 1214our $VERBOSE;
1137 1215
1138BEGIN { 1216BEGIN {
1139 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }"; 1217 require "AnyEvent/constants.pl";
1218
1140 eval "sub TAINT(){ " . (${^TAINT}*1) . " }"; 1219 eval "sub TAINT (){" . (${^TAINT}*1) . "}";
1141 1220
1142 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV} 1221 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
1143 if ${^TAINT}; 1222 if ${^TAINT};
1144 1223
1145 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1; 1224 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
1155 $PROTOCOL{$_} = ++$idx 1234 $PROTOCOL{$_} = ++$idx
1156 for reverse split /\s*,\s*/, 1235 for reverse split /\s*,\s*/,
1157 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; 1236 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
1158} 1237}
1159 1238
1239our @post_detect;
1240
1241sub post_detect(&) {
1242 my ($cb) = @_;
1243
1244 push @post_detect, $cb;
1245
1246 defined wantarray
1247 ? bless \$cb, "AnyEvent::Util::postdetect"
1248 : ()
1249}
1250
1251sub AnyEvent::Util::postdetect::DESTROY {
1252 @post_detect = grep $_ != ${$_[0]}, @post_detect;
1253}
1254
1255our $POSTPONE_W;
1256our @POSTPONE;
1257
1258sub _postpone_exec {
1259 undef $POSTPONE_W;
1260
1261 &{ shift @POSTPONE }
1262 while @POSTPONE;
1263}
1264
1265sub postpone(&) {
1266 push @POSTPONE, shift;
1267
1268 $POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
1269
1270 ()
1271}
1272
1160my @models = ( 1273our @models = (
1161 [EV:: => AnyEvent::Impl::EV:: , 1], 1274 [EV:: => AnyEvent::Impl::EV:: , 1],
1162 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1], 1275 [AnyEvent::Loop:: => AnyEvent::Impl::Perl:: , 1],
1163 # everything below here will not (normally) be autoprobed 1276 # everything below here will not (normally) be autoprobed
1164 # as the pureperl backend should work everywhere 1277 # as the pure perl backend should work everywhere
1165 # and is usually faster 1278 # and is usually faster
1166 [Event:: => AnyEvent::Impl::Event::, 1], 1279 [Event:: => AnyEvent::Impl::Event::, 1],
1167 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers 1280 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
1168 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy 1281 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
1169 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package 1282 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
1170 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles 1283 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
1171 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program 1284 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program
1172 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 1285 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
1173 [Wx:: => AnyEvent::Impl::POE::], 1286 [Wx:: => AnyEvent::Impl::POE::],
1174 [Prima:: => AnyEvent::Impl::POE::], 1287 [Prima:: => AnyEvent::Impl::POE::],
1175 # IO::Async is just too broken - we would need workarounds for its 1288 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # a bitch to autodetect
1176 # byzantine signal and broken child handling, among others. 1289 [Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
1177 # IO::Async is rather hard to detect, as it doesn't have any 1290 [FLTK:: => AnyEvent::Impl::FLTK2::],
1178 # obvious default class.
1179 [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
1180 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
1181 [IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
1182 [AnyEvent::Impl::IOAsync:: => AnyEvent::Impl::IOAsync::], # requires special main program
1183); 1291);
1184 1292
1185our %method = map +($_ => 1), 1293# all autoloaded methods reserve the complete glob, not just the method slot.
1294# due to bugs in perls method cache implementation.
1186 qw(io timer time now now_update signal child idle condvar one_event DESTROY); 1295our @methods = qw(io timer time now now_update signal child idle condvar);
1187 1296
1188our @post_detect;
1189
1190sub post_detect(&) { 1297sub detect() {
1191 my ($cb) = @_; 1298 local $!; # for good measure
1299 local $SIG{__DIE__}; # we use eval
1192 1300
1193 if ($MODEL) { 1301 # free some memory
1194 $cb->(); 1302 *detect = sub () { $MODEL };
1303 # undef &func doesn't correctly update the method cache. grmbl.
1304 # so we delete the whole glob. grmbl.
1305 # otoh, perl doesn't let me undef an active usb, but it lets me free
1306 # a glob with an active sub. hrm. i hope it works, but perl is
1307 # usually buggy in this department. sigh.
1308 delete @{"AnyEvent::"}{@methods};
1309 undef @methods;
1195 1310
1196 undef 1311 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z0-9:]+)$/) {
1312 my $model = $1;
1313 $model = "AnyEvent::Impl::$model" unless $model =~ s/::$//;
1314 if (eval "require $model") {
1315 $MODEL = $model;
1316 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
1197 } else { 1317 } else {
1198 push @post_detect, $cb; 1318 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
1199 1319 }
1200 defined wantarray
1201 ? bless \$cb, "AnyEvent::Util::postdetect"
1202 : ()
1203 } 1320 }
1204}
1205 1321
1206sub AnyEvent::Util::postdetect::DESTROY { 1322 # check for already loaded models
1207 @post_detect = grep $_ != ${$_[0]}, @post_detect;
1208}
1209
1210sub detect() {
1211 unless ($MODEL) { 1323 unless ($MODEL) {
1212 local $SIG{__DIE__}; 1324 for (@REGISTRY, @models) {
1213 1325 my ($package, $model) = @$_;
1214 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 1326 if (${"$package\::VERSION"} > 0) {
1215 my $model = "AnyEvent::Impl::$1";
1216 if (eval "require $model") { 1327 if (eval "require $model") {
1217 $MODEL = $model; 1328 $MODEL = $model;
1218 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2; 1329 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
1219 } else { 1330 last;
1220 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE; 1331 }
1221 } 1332 }
1222 } 1333 }
1223 1334
1224 # check for already loaded models
1225 unless ($MODEL) { 1335 unless ($MODEL) {
1336 # try to autoload a model
1226 for (@REGISTRY, @models) { 1337 for (@REGISTRY, @models) {
1227 my ($package, $model) = @$_; 1338 my ($package, $model, $autoload) = @$_;
1339 if (
1340 $autoload
1341 and eval "require $package"
1228 if (${"$package\::VERSION"} > 0) { 1342 and ${"$package\::VERSION"} > 0
1229 if (eval "require $model") { 1343 and eval "require $model"
1344 ) {
1230 $MODEL = $model; 1345 $MODEL = $model;
1231 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2; 1346 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1232 last; 1347 last;
1233 }
1234 } 1348 }
1235 } 1349 }
1236 1350
1237 unless ($MODEL) {
1238 # try to autoload a model
1239 for (@REGISTRY, @models) {
1240 my ($package, $model, $autoload) = @$_;
1241 if (
1242 $autoload
1243 and eval "require $package"
1244 and ${"$package\::VERSION"} > 0
1245 and eval "require $model"
1246 ) {
1247 $MODEL = $model;
1248 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1249 last;
1250 }
1251 }
1252
1253 $MODEL 1351 $MODEL
1254 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n"; 1352 or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?\n";
1255 }
1256 } 1353 }
1257
1258 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1259
1260 unshift @ISA, $MODEL;
1261
1262 require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
1263
1264 (shift @post_detect)->() while @post_detect;
1265 } 1354 }
1266 1355
1356 # free memory only needed for probing
1357 undef @models;
1358 undef @REGISTRY;
1359
1360 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1361 unshift @ISA, $MODEL;
1362
1363 # now nuke some methods that are overridden by the backend.
1364 # SUPER usage is not allowed in these.
1365 for (qw(time signal child idle)) {
1366 undef &{"AnyEvent::Base::$_"}
1367 if defined &{"$MODEL\::$_"};
1368 }
1369
1370 if ($ENV{PERL_ANYEVENT_STRICT}) {
1371 require AnyEvent::Strict;
1372 }
1373
1374 if ($ENV{PERL_ANYEVENT_DEBUG_WRAP}) {
1375 require AnyEvent::Debug;
1376 AnyEvent::Debug::wrap ($ENV{PERL_ANYEVENT_DEBUG_WRAP});
1377 }
1378
1379 if (exists $ENV{PERL_ANYEVENT_DEBUG_SHELL}) {
1380 require AnyEvent::Socket;
1381 require AnyEvent::Debug;
1382
1383 my ($host, $service) = AnyEvent::Socket::parse_hostport ($ENV{PERL_ANYEVENT_DEBUG_SHELL});
1384 $AnyEvent::Debug::SHELL = AnyEvent::Debug::shell ($host, $service);
1385 }
1386
1387 (shift @post_detect)->() while @post_detect;
1388 undef @post_detect;
1389
1390 *post_detect = sub(&) {
1391 shift->();
1392
1393 undef
1394 };
1395
1267 $MODEL 1396 $MODEL
1268} 1397}
1269 1398
1270sub AUTOLOAD { 1399for my $name (@methods) {
1271 (my $func = $AUTOLOAD) =~ s/.*://; 1400 *$name = sub {
1272 1401 detect;
1273 $method{$func} 1402 # we use goto because
1274 or Carp::croak "$func: not a valid method for AnyEvent objects"; 1403 # a) it makes the thunk more transparent
1275 1404 # b) it allows us to delete the thunk later
1276 detect unless $MODEL; 1405 goto &{ UNIVERSAL::can AnyEvent => "SUPER::$name" }
1277 1406 };
1278 my $class = shift;
1279 $class->$func (@_);
1280} 1407}
1281 1408
1282# utility function to dup a filehandle. this is used by many backends 1409# utility function to dup a filehandle. this is used by many backends
1283# to support binding more than one watcher per filehandle (they usually 1410# to support binding more than one watcher per filehandle (they usually
1284# allow only one watcher per fd, so we dup it to get a different one). 1411# allow only one watcher per fd, so we dup it to get a different one).
1298 1425
1299=head1 SIMPLIFIED AE API 1426=head1 SIMPLIFIED AE API
1300 1427
1301Starting with version 5.0, AnyEvent officially supports a second, much 1428Starting with version 5.0, AnyEvent officially supports a second, much
1302simpler, API that is designed to reduce the calling, typing and memory 1429simpler, API that is designed to reduce the calling, typing and memory
1303overhead. 1430overhead by using function call syntax and a fixed number of parameters.
1304 1431
1305See the L<AE> manpage for details. 1432See the L<AE> manpage for details.
1306 1433
1307=cut 1434=cut
1308 1435
1309package AE; 1436package AE;
1310 1437
1311our $VERSION = $AnyEvent::VERSION; 1438our $VERSION = $AnyEvent::VERSION;
1312 1439
1440sub _reset() {
1441 eval q{
1442 # fall back to the main API by default - backends and AnyEvent::Base
1443 # implementations can overwrite these.
1444
1313sub io($$$) { 1445 sub io($$$) {
1314 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2]) 1446 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
1315} 1447 }
1316 1448
1317sub timer($$$) { 1449 sub timer($$$) {
1318 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2]) 1450 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
1319} 1451 }
1320 1452
1321sub signal($$) { 1453 sub signal($$) {
1322 AnyEvent->signal (signal => $_[0], cb => $_[1]) 1454 AnyEvent->signal (signal => $_[0], cb => $_[1])
1323} 1455 }
1324 1456
1325sub child($$) { 1457 sub child($$) {
1326 AnyEvent->child (pid => $_[0], cb => $_[1]) 1458 AnyEvent->child (pid => $_[0], cb => $_[1])
1327} 1459 }
1328 1460
1329sub idle($) { 1461 sub idle($) {
1330 AnyEvent->idle (cb => $_[0]) 1462 AnyEvent->idle (cb => $_[0]);
1331} 1463 }
1332 1464
1333sub cv(;&) { 1465 sub cv(;&) {
1334 AnyEvent->condvar (@_ ? (cb => $_[0]) : ()) 1466 AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
1335} 1467 }
1336 1468
1337sub now() { 1469 sub now() {
1338 AnyEvent->now 1470 AnyEvent->now
1339} 1471 }
1340 1472
1341sub now_update() { 1473 sub now_update() {
1342 AnyEvent->now_update 1474 AnyEvent->now_update
1343} 1475 }
1344 1476
1345sub time() { 1477 sub time() {
1346 AnyEvent->time 1478 AnyEvent->time
1479 }
1480
1481 *postpone = \&AnyEvent::postpone;
1482 };
1483 die if $@;
1347} 1484}
1485
1486BEGIN { _reset }
1348 1487
1349package AnyEvent::Base; 1488package AnyEvent::Base;
1350 1489
1351# default implementations for many methods 1490# default implementations for many methods
1352 1491
1353sub _time() { 1492sub time {
1493 eval q{ # poor man's autoloading {}
1354 # probe for availability of Time::HiRes 1494 # probe for availability of Time::HiRes
1355 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") { 1495 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
1356 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8; 1496 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
1357 *_time = \&Time::HiRes::time; 1497 *AE::time = \&Time::HiRes::time;
1358 # if (eval "use POSIX (); (POSIX::times())... 1498 # if (eval "use POSIX (); (POSIX::times())...
1359 } else { 1499 } else {
1360 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE; 1500 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
1361 *_time = sub { time }; # epic fail 1501 *AE::time = sub (){ time }; # epic fail
1502 }
1503
1504 *time = sub { AE::time }; # different prototypes
1362 } 1505 };
1506 die if $@;
1363 1507
1364 &_time 1508 &time
1365} 1509}
1366 1510
1367sub time { _time } 1511*now = \&time;
1368sub now { _time } 1512
1369sub now_update { } 1513sub now_update { }
1370 1514
1515sub _poll {
1516 Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
1517}
1518
1371# default implementation for ->condvar 1519# default implementation for ->condvar
1520# in fact, the default should not be overwritten
1372 1521
1373sub condvar { 1522sub condvar {
1523 eval q{ # poor man's autoloading {}
1524 *condvar = sub {
1374 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar" 1525 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1526 };
1527
1528 *AE::cv = sub (;&) {
1529 bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
1530 };
1531 };
1532 die if $@;
1533
1534 &condvar
1375} 1535}
1376 1536
1377# default implementation for ->signal 1537# default implementation for ->signal
1378 1538
1379our $HAVE_ASYNC_INTERRUPT; 1539our $HAVE_ASYNC_INTERRUPT;
1388 1548
1389our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO); 1549our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
1390our (%SIG_ASY, %SIG_ASY_W); 1550our (%SIG_ASY, %SIG_ASY_W);
1391our ($SIG_COUNT, $SIG_TW); 1551our ($SIG_COUNT, $SIG_TW);
1392 1552
1393sub _signal_exec {
1394 $HAVE_ASYNC_INTERRUPT
1395 ? $SIGPIPE_R->drain
1396 : sysread $SIGPIPE_R, (my $dummy), 9;
1397
1398 while (%SIG_EV) {
1399 for (keys %SIG_EV) {
1400 delete $SIG_EV{$_};
1401 $_->() for values %{ $SIG_CB{$_} || {} };
1402 }
1403 }
1404}
1405
1406# install a dummy wakeup watcher to reduce signal catching latency 1553# install a dummy wakeup watcher to reduce signal catching latency
1554# used by Impls
1407sub _sig_add() { 1555sub _sig_add() {
1408 unless ($SIG_COUNT++) { 1556 unless ($SIG_COUNT++) {
1409 # try to align timer on a full-second boundary, if possible 1557 # try to align timer on a full-second boundary, if possible
1410 my $NOW = AE::now; 1558 my $NOW = AE::now;
1411 1559
1421 undef $SIG_TW 1569 undef $SIG_TW
1422 unless --$SIG_COUNT; 1570 unless --$SIG_COUNT;
1423} 1571}
1424 1572
1425our $_sig_name_init; $_sig_name_init = sub { 1573our $_sig_name_init; $_sig_name_init = sub {
1426 eval q{ # poor man's autoloading 1574 eval q{ # poor man's autoloading {}
1427 undef $_sig_name_init; 1575 undef $_sig_name_init;
1428 1576
1429 if (_have_async_interrupt) { 1577 if (_have_async_interrupt) {
1430 *sig2num = \&Async::Interrupt::sig2num; 1578 *sig2num = \&Async::Interrupt::sig2num;
1431 *sig2name = \&Async::Interrupt::sig2name; 1579 *sig2name = \&Async::Interrupt::sig2name;
1463 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec; 1611 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
1464 1612
1465 } else { 1613 } else {
1466 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8; 1614 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
1467 1615
1468 require Fcntl;
1469
1470 if (AnyEvent::WIN32) { 1616 if (AnyEvent::WIN32) {
1471 require AnyEvent::Util; 1617 require AnyEvent::Util;
1472 1618
1473 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe (); 1619 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1474 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R; 1620 AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
1475 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case 1621 AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
1476 } else { 1622 } else {
1477 pipe $SIGPIPE_R, $SIGPIPE_W; 1623 pipe $SIGPIPE_R, $SIGPIPE_W;
1478 fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R; 1624 fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
1479 fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case 1625 fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
1480 1626
1481 # not strictly required, as $^F is normally 2, but let's make sure... 1627 # not strictly required, as $^F is normally 2, but let's make sure...
1482 fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC; 1628 fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
1483 fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC; 1629 fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
1484 } 1630 }
1485 1631
1486 $SIGPIPE_R 1632 $SIGPIPE_R
1487 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n"; 1633 or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
1488 1634
1489 $SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec; 1635 $SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
1490 } 1636 }
1491 1637
1492 *signal = sub { 1638 *signal = $HAVE_ASYNC_INTERRUPT
1639 ? sub {
1493 my (undef, %arg) = @_; 1640 my (undef, %arg) = @_;
1494 1641
1495 my $signal = uc $arg{signal}
1496 or Carp::croak "required option 'signal' is missing";
1497
1498 if ($HAVE_ASYNC_INTERRUPT) {
1499 # async::interrupt 1642 # async::interrupt
1500
1501 $signal = sig2num $signal; 1643 my $signal = sig2num $arg{signal};
1502 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1644 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1503 1645
1504 $SIG_ASY{$signal} ||= new Async::Interrupt 1646 $SIG_ASY{$signal} ||= new Async::Interrupt
1505 cb => sub { undef $SIG_EV{$signal} }, 1647 cb => sub { undef $SIG_EV{$signal} },
1506 signal => $signal, 1648 signal => $signal,
1507 pipe => [$SIGPIPE_R->filenos], 1649 pipe => [$SIGPIPE_R->filenos],
1508 pipe_autodrain => 0, 1650 pipe_autodrain => 0,
1509 ; 1651 ;
1510 1652
1511 } else { 1653 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1654 }
1655 : sub {
1656 my (undef, %arg) = @_;
1657
1512 # pure perl 1658 # pure perl
1513
1514 # AE::Util has been loaded in signal
1515 $signal = sig2name $signal; 1659 my $signal = sig2name $arg{signal};
1516 $SIG_CB{$signal}{$arg{cb}} = $arg{cb}; 1660 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
1517 1661
1518 $SIG{$signal} ||= sub { 1662 $SIG{$signal} ||= sub {
1519 local $!; 1663 local $!;
1520 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV; 1664 syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
1521 undef $SIG_EV{$signal}; 1665 undef $SIG_EV{$signal};
1522 }; 1666 };
1523 1667
1524 # can't do signal processing without introducing races in pure perl, 1668 # can't do signal processing without introducing races in pure perl,
1525 # so limit the signal latency. 1669 # so limit the signal latency.
1526 _sig_add; 1670 _sig_add;
1527 }
1528 1671
1529 bless [$signal, $arg{cb}], "AnyEvent::Base::signal" 1672 bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
1673 }
1530 }; 1674 ;
1531 1675
1532 *AnyEvent::Base::signal::DESTROY = sub { 1676 *AnyEvent::Base::signal::DESTROY = sub {
1533 my ($signal, $cb) = @{$_[0]}; 1677 my ($signal, $cb) = @{$_[0]};
1534 1678
1535 _sig_del; 1679 _sig_del;
1542 # print weird messages, or just unconditionally exit 1686 # print weird messages, or just unconditionally exit
1543 # instead of getting the default action. 1687 # instead of getting the default action.
1544 undef $SIG{$signal} 1688 undef $SIG{$signal}
1545 unless keys %{ $SIG_CB{$signal} }; 1689 unless keys %{ $SIG_CB{$signal} };
1546 }; 1690 };
1691
1692 *_signal_exec = sub {
1693 $HAVE_ASYNC_INTERRUPT
1694 ? $SIGPIPE_R->drain
1695 : sysread $SIGPIPE_R, (my $dummy), 9;
1696
1697 while (%SIG_EV) {
1698 for (keys %SIG_EV) {
1699 delete $SIG_EV{$_};
1700 &$_ for values %{ $SIG_CB{$_} || {} };
1701 }
1702 }
1703 };
1547 }; 1704 };
1548 die if $@; 1705 die if $@;
1706
1549 &signal 1707 &signal
1550} 1708}
1551 1709
1552# default implementation for ->child 1710# default implementation for ->child
1553 1711
1554our %PID_CB; 1712our %PID_CB;
1555our $CHLD_W; 1713our $CHLD_W;
1556our $CHLD_DELAY_W; 1714our $CHLD_DELAY_W;
1557our $WNOHANG;
1558 1715
1716# used by many Impl's
1559sub _emit_childstatus($$) { 1717sub _emit_childstatus($$) {
1560 my (undef, $rpid, $rstatus) = @_; 1718 my (undef, $rpid, $rstatus) = @_;
1561 1719
1562 $_->($rpid, $rstatus) 1720 $_->($rpid, $rstatus)
1563 for values %{ $PID_CB{$rpid} || {} }, 1721 for values %{ $PID_CB{$rpid} || {} },
1564 values %{ $PID_CB{0} || {} }; 1722 values %{ $PID_CB{0} || {} };
1565} 1723}
1566 1724
1567sub _sigchld {
1568 my $pid;
1569
1570 AnyEvent->_emit_childstatus ($pid, $?)
1571 while ($pid = waitpid -1, $WNOHANG) > 0;
1572}
1573
1574sub child { 1725sub child {
1726 eval q{ # poor man's autoloading {}
1727 *_sigchld = sub {
1728 my $pid;
1729
1730 AnyEvent->_emit_childstatus ($pid, $?)
1731 while ($pid = waitpid -1, WNOHANG) > 0;
1732 };
1733
1734 *child = sub {
1575 my (undef, %arg) = @_; 1735 my (undef, %arg) = @_;
1576 1736
1577 defined (my $pid = $arg{pid} + 0) 1737 my $pid = $arg{pid};
1578 or Carp::croak "required option 'pid' is missing"; 1738 my $cb = $arg{cb};
1579 1739
1580 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 1740 $PID_CB{$pid}{$cb+0} = $cb;
1581 1741
1582 # WNOHANG is almost cetrainly 1 everywhere
1583 $WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
1584 ? 1
1585 : eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1586
1587 unless ($CHLD_W) { 1742 unless ($CHLD_W) {
1588 $CHLD_W = AE::signal CHLD => \&_sigchld; 1743 $CHLD_W = AE::signal CHLD => \&_sigchld;
1589 # child could be a zombie already, so make at least one round 1744 # child could be a zombie already, so make at least one round
1590 &_sigchld; 1745 &_sigchld;
1591 } 1746 }
1592 1747
1593 bless [$pid, $arg{cb}], "AnyEvent::Base::child" 1748 bless [$pid, $cb+0], "AnyEvent::Base::child"
1594} 1749 };
1595 1750
1596sub AnyEvent::Base::child::DESTROY { 1751 *AnyEvent::Base::child::DESTROY = sub {
1597 my ($pid, $cb) = @{$_[0]}; 1752 my ($pid, $icb) = @{$_[0]};
1598 1753
1599 delete $PID_CB{$pid}{$cb}; 1754 delete $PID_CB{$pid}{$icb};
1600 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 1755 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1601 1756
1602 undef $CHLD_W unless keys %PID_CB; 1757 undef $CHLD_W unless keys %PID_CB;
1758 };
1759 };
1760 die if $@;
1761
1762 &child
1603} 1763}
1604 1764
1605# idle emulation is done by simply using a timer, regardless 1765# idle emulation is done by simply using a timer, regardless
1606# of whether the process is idle or not, and not letting 1766# of whether the process is idle or not, and not letting
1607# the callback use more than 50% of the time. 1767# the callback use more than 50% of the time.
1608sub idle { 1768sub idle {
1769 eval q{ # poor man's autoloading {}
1770 *idle = sub {
1609 my (undef, %arg) = @_; 1771 my (undef, %arg) = @_;
1610 1772
1611 my ($cb, $w, $rcb) = $arg{cb}; 1773 my ($cb, $w, $rcb) = $arg{cb};
1612 1774
1613 $rcb = sub { 1775 $rcb = sub {
1614 if ($cb) { 1776 if ($cb) {
1615 $w = _time; 1777 $w = AE::time;
1616 &$cb; 1778 &$cb;
1617 $w = _time - $w; 1779 $w = AE::time - $w;
1618 1780
1619 # never use more then 50% of the time for the idle watcher, 1781 # never use more then 50% of the time for the idle watcher,
1620 # within some limits 1782 # within some limits
1621 $w = 0.0001 if $w < 0.0001; 1783 $w = 0.0001 if $w < 0.0001;
1622 $w = 5 if $w > 5; 1784 $w = 5 if $w > 5;
1623 1785
1624 $w = AE::timer $w, 0, $rcb; 1786 $w = AE::timer $w, 0, $rcb;
1625 } else { 1787 } else {
1626 # clean up... 1788 # clean up...
1627 undef $w; 1789 undef $w;
1628 undef $rcb; 1790 undef $rcb;
1791 }
1792 };
1793
1794 $w = AE::timer 0.05, 0, $rcb;
1795
1796 bless \\$cb, "AnyEvent::Base::idle"
1629 } 1797 };
1798
1799 *AnyEvent::Base::idle::DESTROY = sub {
1800 undef $${$_[0]};
1801 };
1630 }; 1802 };
1803 die if $@;
1631 1804
1632 $w = AE::timer 0.05, 0, $rcb; 1805 &idle
1633
1634 bless \\$cb, "AnyEvent::Base::idle"
1635}
1636
1637sub AnyEvent::Base::idle::DESTROY {
1638 undef $${$_[0]};
1639} 1806}
1640 1807
1641package AnyEvent::CondVar; 1808package AnyEvent::CondVar;
1642 1809
1643our @ISA = AnyEvent::CondVar::Base::; 1810our @ISA = AnyEvent::CondVar::Base::;
1811
1812# only to be used for subclassing
1813sub new {
1814 my $class = shift;
1815 bless AnyEvent->condvar (@_), $class
1816}
1644 1817
1645package AnyEvent::CondVar::Base; 1818package AnyEvent::CondVar::Base;
1646 1819
1647#use overload 1820#use overload
1648# '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, 1821# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1658 1831
1659sub _send { 1832sub _send {
1660 # nop 1833 # nop
1661} 1834}
1662 1835
1836sub _wait {
1837 AnyEvent->_poll until $_[0]{_ae_sent};
1838}
1839
1663sub send { 1840sub send {
1664 my $cv = shift; 1841 my $cv = shift;
1665 $cv->{_ae_sent} = [@_]; 1842 $cv->{_ae_sent} = [@_];
1666 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb}; 1843 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb};
1667 $cv->_send; 1844 $cv->_send;
1674 1851
1675sub ready { 1852sub ready {
1676 $_[0]{_ae_sent} 1853 $_[0]{_ae_sent}
1677} 1854}
1678 1855
1679sub _wait {
1680 $WAITING
1681 and !$_[0]{_ae_sent}
1682 and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
1683
1684 local $WAITING = 1;
1685 AnyEvent->one_event while !$_[0]{_ae_sent};
1686}
1687
1688sub recv { 1856sub recv {
1857 unless ($_[0]{_ae_sent}) {
1858 $WAITING
1859 and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
1860
1861 local $WAITING = 1;
1689 $_[0]->_wait; 1862 $_[0]->_wait;
1863 }
1690 1864
1691 Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; 1865 $_[0]{_ae_croak}
1692 wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] 1866 and Carp::croak $_[0]{_ae_croak};
1867
1868 wantarray
1869 ? @{ $_[0]{_ae_sent} }
1870 : $_[0]{_ae_sent}[0]
1693} 1871}
1694 1872
1695sub cb { 1873sub cb {
1696 my $cv = shift; 1874 my $cv = shift;
1697 1875
1713 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } }; 1891 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1714} 1892}
1715 1893
1716# undocumented/compatibility with pre-3.4 1894# undocumented/compatibility with pre-3.4
1717*broadcast = \&send; 1895*broadcast = \&send;
1718*wait = \&_wait; 1896*wait = \&recv;
1719 1897
1720=head1 ERROR AND EXCEPTION HANDLING 1898=head1 ERROR AND EXCEPTION HANDLING
1721 1899
1722In general, AnyEvent does not do any error handling - it relies on the 1900In general, AnyEvent does not do any error handling - it relies on the
1723caller to do that if required. The L<AnyEvent::Strict> module (see also 1901caller to do that if required. The L<AnyEvent::Strict> module (see also
1770check the arguments passed to most method calls. If it finds any problems, 1948check the arguments passed to most method calls. If it finds any problems,
1771it will croak. 1949it will croak.
1772 1950
1773In other words, enables "strict" mode. 1951In other words, enables "strict" mode.
1774 1952
1775Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense> 1953Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
1776>>, it is definitely recommended to keep it off in production. Keeping 1954>>, it is definitely recommended to keep it off in production. Keeping
1777C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs 1955C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
1778can be very useful, however. 1956can be very useful, however.
1779 1957
1958=item C<PERL_ANYEVENT_DEBUG_SHELL>
1959
1960If this env variable is set, then its contents will be
1961interpreted by C<AnyEvent::Socket::parse_hostport> and an
1962C<AnyEvent::Debug::shell> is bound on that port. The shell object is saved
1963in C<$AnyEvent::Debug::SHELL>.
1964
1965For example, to bind a debug shell on a unix domain socket in
1966F</tmp/debug.sock>, you could use this:
1967
1968 PERL_ANYEVENT_DEBUG_SHELL=unix/:/tmp/debug.sock perlprog
1969
1970=item C<PERL_ANYEVENT_DEBUG_WRAP>
1971
1972Can be set to C<0>, C<1> or C<2> and enables wrapping of all watchers for
1973debugging purposes. See C<AnyEvent::Debug::wrap> for details.
1974
1780=item C<PERL_ANYEVENT_MODEL> 1975=item C<PERL_ANYEVENT_MODEL>
1781 1976
1782This can be used to specify the event model to be used by AnyEvent, before 1977This can be used to specify the event model to be used by AnyEvent, before
1783auto detection and -probing kicks in. It must be a string consisting 1978auto detection and -probing kicks in.
1784entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended 1979
1980It normally is a string consisting entirely of ASCII letters (e.g. C<EV>
1981or C<IOAsync>). The string C<AnyEvent::Impl::> gets prepended and the
1785and the resulting module name is loaded and if the load was successful, 1982resulting module name is loaded and - if the load was successful - used as
1786used as event model. If it fails to load AnyEvent will proceed with 1983event model backend. If it fails to load then AnyEvent will proceed with
1787auto detection and -probing. 1984auto detection and -probing.
1788 1985
1789This functionality might change in future versions. 1986If the string ends with C<::> instead (e.g. C<AnyEvent::Impl::EV::>) then
1987nothing gets prepended and the module name is used as-is (hint: C<::> at
1988the end of a string designates a module name and quotes it appropriately).
1790 1989
1791For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you 1990For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
1792could start your program like this: 1991could start your program like this:
1793 1992
1794 PERL_ANYEVENT_MODEL=Perl perl ... 1993 PERL_ANYEVENT_MODEL=Perl perl ...
1795 1994
1796=item C<PERL_ANYEVENT_PROTOCOLS> 1995=item C<PERL_ANYEVENT_PROTOCOLS>
2002 2201
2003The actual code goes further and collects all errors (C<die>s, exceptions) 2202The actual code goes further and collects all errors (C<die>s, exceptions)
2004that occurred during request processing. The C<result> method detects 2203that occurred during request processing. The C<result> method detects
2005whether an exception as thrown (it is stored inside the $txn object) 2204whether an exception as thrown (it is stored inside the $txn object)
2006and just throws the exception, which means connection errors and other 2205and just throws the exception, which means connection errors and other
2007problems get reported tot he code that tries to use the result, not in a 2206problems get reported to the code that tries to use the result, not in a
2008random callback. 2207random callback.
2009 2208
2010All of this enables the following usage styles: 2209All of this enables the following usage styles:
2011 2210
20121. Blocking: 22111. Blocking:
2426 unless defined $SIG{PIPE}; 2625 unless defined $SIG{PIPE};
2427 2626
2428=head1 RECOMMENDED/OPTIONAL MODULES 2627=head1 RECOMMENDED/OPTIONAL MODULES
2429 2628
2430One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and 2629One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
2431it's built-in modules) are required to use it. 2630its built-in modules) are required to use it.
2432 2631
2433That does not mean that AnyEvent won't take advantage of some additional 2632That does not mean that AnyEvent won't take advantage of some additional
2434modules if they are installed. 2633modules if they are installed.
2435 2634
2436This section epxlains which additional modules will be used, and how they 2635This section explains which additional modules will be used, and how they
2437affect AnyEvent's operetion. 2636affect AnyEvent's operation.
2438 2637
2439=over 4 2638=over 4
2440 2639
2441=item L<Async::Interrupt> 2640=item L<Async::Interrupt>
2442 2641
2447catch the signals) with some delay (default is 10 seconds, look for 2646catch the signals) with some delay (default is 10 seconds, look for
2448C<$AnyEvent::MAX_SIGNAL_LATENCY>). 2647C<$AnyEvent::MAX_SIGNAL_LATENCY>).
2449 2648
2450If this module is available, then it will be used to implement signal 2649If this module is available, then it will be used to implement signal
2451catching, which means that signals will not be delayed, and the event loop 2650catching, which means that signals will not be delayed, and the event loop
2452will not be interrupted regularly, which is more efficient (And good for 2651will not be interrupted regularly, which is more efficient (and good for
2453battery life on laptops). 2652battery life on laptops).
2454 2653
2455This affects not just the pure-perl event loop, but also other event loops 2654This affects not just the pure-perl event loop, but also other event loops
2456that have no signal handling on their own (e.g. Glib, Tk, Qt). 2655that have no signal handling on their own (e.g. Glib, Tk, Qt).
2457 2656
2469automatic timer adjustments even when no monotonic clock is available, 2668automatic timer adjustments even when no monotonic clock is available,
2470can take avdantage of advanced kernel interfaces such as C<epoll> and 2669can take avdantage of advanced kernel interfaces such as C<epoll> and
2471C<kqueue>, and is the fastest backend I<by far>. You can even embed 2670C<kqueue>, and is the fastest backend I<by far>. You can even embed
2472L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>). 2671L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
2473 2672
2673If you only use backends that rely on another event loop (e.g. C<Tk>),
2674then this module will do nothing for you.
2675
2474=item L<Guard> 2676=item L<Guard>
2475 2677
2476The guard module, when used, will be used to implement 2678The guard module, when used, will be used to implement
2477C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a 2679C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
2478lot less memory), but otherwise doesn't affect guard operation much. It is 2680lot less memory), but otherwise doesn't affect guard operation much. It is
2479purely used for performance. 2681purely used for performance.
2480 2682
2481=item L<JSON> and L<JSON::XS> 2683=item L<JSON> and L<JSON::XS>
2482 2684
2483One of these modules is required when you want to read or write JSON data 2685One of these modules is required when you want to read or write JSON data
2484via L<AnyEvent::Handle>. It is also written in pure-perl, but can take 2686via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
2485advantage of the ultra-high-speed L<JSON::XS> module when it is installed. 2687advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
2486
2487In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
2488installed.
2489 2688
2490=item L<Net::SSLeay> 2689=item L<Net::SSLeay>
2491 2690
2492Implementing TLS/SSL in Perl is certainly interesting, but not very 2691Implementing TLS/SSL in Perl is certainly interesting, but not very
2493worthwhile: If this module is installed, then L<AnyEvent::Handle> (with 2692worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
2494the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL. 2693the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
2495 2694
2496=item L<Time::HiRes> 2695=item L<Time::HiRes>
2497 2696
2498This module is part of perl since release 5.008. It will be used when the 2697This module is part of perl since release 5.008. It will be used when the
2499chosen event library does not come with a timing source on it's own. The 2698chosen event library does not come with a timing source of its own. The
2500pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to 2699pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
2501try to use a monotonic clock for timing stability. 2700try to use a monotonic clock for timing stability.
2502 2701
2503=back 2702=back
2504 2703
2505 2704
2506=head1 FORK 2705=head1 FORK
2507 2706
2508Most event libraries are not fork-safe. The ones who are usually are 2707Most event libraries are not fork-safe. The ones who are usually are
2509because they rely on inefficient but fork-safe C<select> or C<poll> 2708because they rely on inefficient but fork-safe C<select> or C<poll> calls
2510calls. Only L<EV> is fully fork-aware. 2709- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
2710are usually badly thought-out hacks that are incompatible with fork in
2711one way or another. Only L<EV> is fully fork-aware and ensures that you
2712continue event-processing in both parent and child (or both, if you know
2713what you are doing).
2714
2715This means that, in general, you cannot fork and do event processing in
2716the child if the event library was initialised before the fork (which
2717usually happens when the first AnyEvent watcher is created, or the library
2718is loaded).
2511 2719
2512If you have to fork, you must either do so I<before> creating your first 2720If you have to fork, you must either do so I<before> creating your first
2513watcher OR you must not use AnyEvent at all in the child OR you must do 2721watcher OR you must not use AnyEvent at all in the child OR you must do
2514something completely out of the scope of AnyEvent. 2722something completely out of the scope of AnyEvent.
2723
2724The problem of doing event processing in the parent I<and> the child
2725is much more complicated: even for backends that I<are> fork-aware or
2726fork-safe, their behaviour is not usually what you want: fork clones all
2727watchers, that means all timers, I/O watchers etc. are active in both
2728parent and child, which is almost never what you want. USing C<exec>
2729to start worker children from some kind of manage rprocess is usually
2730preferred, because it is much easier and cleaner, at the expense of having
2731to have another binary.
2515 2732
2516 2733
2517=head1 SECURITY CONSIDERATIONS 2734=head1 SECURITY CONSIDERATIONS
2518 2735
2519AnyEvent can be forced to load any event model via 2736AnyEvent can be forced to load any event model via
2549pronounced). 2766pronounced).
2550 2767
2551 2768
2552=head1 SEE ALSO 2769=head1 SEE ALSO
2553 2770
2771Tutorial/Introduction: L<AnyEvent::Intro>.
2772
2773FAQ: L<AnyEvent::FAQ>.
2774
2554Utility functions: L<AnyEvent::Util>. 2775Utility functions: L<AnyEvent::Util>.
2555 2776
2556Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, 2777Event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>, L<Glib::EV>,
2557L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. 2778L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
2558 2779
2559Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, 2780Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
2560L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, 2781L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
2561L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, 2782L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
2562L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>. 2783L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
2564Non-blocking file handles, sockets, TCP clients and 2785Non-blocking file handles, sockets, TCP clients and
2565servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>. 2786servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
2566 2787
2567Asynchronous DNS: L<AnyEvent::DNS>. 2788Asynchronous DNS: L<AnyEvent::DNS>.
2568 2789
2569Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, 2790Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
2570L<Coro::Event>,
2571 2791
2572Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>, 2792Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
2573L<AnyEvent::HTTP>. 2793L<AnyEvent::HTTP>.
2574 2794
2575 2795
2576=head1 AUTHOR 2796=head1 AUTHOR
2577 2797

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines