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.29 by root, Wed Oct 31 14:17:43 2007 UTC vs.
Revision 1.54 by root, Tue Apr 22 05:12:19 2008 UTC

1=head1 NAME 1=head1 NAME
2 2
3AnyEvent - provide framework for multiple event loops 3AnyEvent - provide framework for multiple event loops
4 4
5Event, Coro, Glib, Tk, Perl - various supported event loops 5EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl - various supported event loops
6 6
7=head1 SYNOPSIS 7=head1 SYNOPSIS
8 8
9 use AnyEvent; 9 use AnyEvent;
10 10
… …
14 14
15 my $w = AnyEvent->timer (after => $seconds, cb => sub { 15 my $w = AnyEvent->timer (after => $seconds, cb => sub {
16 ... 16 ...
17 }); 17 });
18 18
19 my $w = AnyEvent->condvar; # stores wether a condition was flagged 19 my $w = AnyEvent->condvar; # stores whether a condition was flagged
20 $w->wait; # enters "main loop" till $condvar gets ->broadcast 20 $w->wait; # enters "main loop" till $condvar gets ->broadcast
21 $w->broadcast; # wake up current and all future wait's 21 $w->broadcast; # wake up current and all future wait's
22
23=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24
25Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26nowadays. So what is different about AnyEvent?
27
28Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
29policy> and AnyEvent is I<small and efficient>.
30
31First and foremost, I<AnyEvent is not an event model> itself, it only
32interfaces to whatever event model the main program happens to use in a
33pragmatic way. For event models and certain classes of immortals alike,
34the statement "there can only be one" is a bitter reality: In general,
35only one event loop can be active at the same time in a process. AnyEvent
36helps hiding the differences between those event loops.
37
38The goal of AnyEvent is to offer module authors the ability to do event
39programming (waiting for I/O or timer events) without subscribing to a
40religion, a way of living, and most importantly: without forcing your
41module users into the same thing by forcing them to use the same event
42model you use.
43
44For modules like POE or IO::Async (which is a total misnomer as it is
45actually doing all I/O I<synchronously>...), using them in your module is
46like joining a cult: After you joined, you are dependent on them and you
47cannot use anything else, as it is simply incompatible to everything that
48isn't itself. What's worse, all the potential users of your module are
49I<also> forced to use the same event loop you use.
50
51AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
52fine. AnyEvent + Tk works fine etc. etc. but none of these work together
53with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if
54your module uses one of those, every user of your module has to use it,
55too. But if your module uses AnyEvent, it works transparently with all
56event models it supports (including stuff like POE and IO::Async, as long
57as those use one of the supported event loops. It is trivial to add new
58event loops to AnyEvent, too, so it is future-proof).
59
60In addition to being free of having to use I<the one and only true event
61model>, AnyEvent also is free of bloat and policy: with POE or similar
62modules, you get an enourmous amount of code and strict rules you have to
63follow. AnyEvent, on the other hand, is lean and up to the point, by only
64offering the functionality that is necessary, in as thin as a wrapper as
65technically possible.
66
67Of course, if you want lots of policy (this can arguably be somewhat
68useful) and you want to force your users to use the one and only event
69model, you should I<not> use this module.
70
22 71
23=head1 DESCRIPTION 72=head1 DESCRIPTION
24 73
25L<AnyEvent> provides an identical interface to multiple event loops. This 74L<AnyEvent> provides an identical interface to multiple event loops. This
26allows module authors to utilise an event loop without forcing module 75allows module authors to utilise an event loop without forcing module
27users to use the same event loop (as only a single event loop can coexist 76users to use the same event loop (as only a single event loop can coexist
28peacefully at any one time). 77peacefully at any one time).
29 78
30The interface itself is vaguely similar but not identical to the Event 79The interface itself is vaguely similar, but not identical to the L<Event>
31module. 80module.
32 81
33On the first call of any method, the module tries to detect the currently 82During the first call of any watcher-creation method, the module tries
34loaded event loop by probing wether any of the following modules is 83to detect the currently loaded event loop by probing whether one of the
35loaded: L<Coro::Event>, L<Event>, L<Glib>, L<Tk>. The first one found is 84following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
36used. If none is found, the module tries to load these modules in the 85L<Event>, L<Glib>, L<Tk>. The first one found is used. If none are found,
37order given. The first one that could be successfully loaded will be 86the module tries to load these modules in the stated order. The first one
38used. If still none could be found, AnyEvent will fall back to a pure-perl 87that can be successfully loaded will be used. If, after this, still none
39event loop, which is also not very efficient. 88could be found, AnyEvent will fall back to a pure-perl event loop, which
89is not very efficient, but should work everywhere.
40 90
41Because AnyEvent first checks for modules that are already loaded, loading 91Because AnyEvent first checks for modules that are already loaded, loading
42an Event model explicitly before first using AnyEvent will likely make 92an event model explicitly before first using AnyEvent will likely make
43that model the default. For example: 93that model the default. For example:
44 94
45 use Tk; 95 use Tk;
46 use AnyEvent; 96 use AnyEvent;
47 97
48 # .. AnyEvent will likely default to Tk 98 # .. AnyEvent will likely default to Tk
99
100The I<likely> means that, if any module loads another event model and
101starts using it, all bets are off. Maybe you should tell their authors to
102use AnyEvent so their modules work together with others seamlessly...
49 103
50The pure-perl implementation of AnyEvent is called 104The pure-perl implementation of AnyEvent is called
51C<AnyEvent::Impl::Perl>. Like other event modules you can load it 105C<AnyEvent::Impl::Perl>. Like other event modules you can load it
52explicitly. 106explicitly.
53 107
… …
56AnyEvent has the central concept of a I<watcher>, which is an object that 110AnyEvent has the central concept of a I<watcher>, which is an object that
57stores relevant data for each kind of event you are waiting for, such as 111stores relevant data for each kind of event you are waiting for, such as
58the callback to call, the filehandle to watch, etc. 112the callback to call, the filehandle to watch, etc.
59 113
60These watchers are normal Perl objects with normal Perl lifetime. After 114These watchers are normal Perl objects with normal Perl lifetime. After
61creating a watcher it will immediately "watch" for events and invoke 115creating a watcher it will immediately "watch" for events and invoke the
116callback when the event occurs (of course, only when the event model
117is in control).
118
62the callback. To disable the watcher you have to destroy it (e.g. by 119To disable the watcher you have to destroy it (e.g. by setting the
63setting the variable that stores it to C<undef> or otherwise deleting all 120variable you store it in to C<undef> or otherwise deleting all references
64references to it). 121to it).
65 122
66All watchers are created by calling a method on the C<AnyEvent> class. 123All watchers are created by calling a method on the C<AnyEvent> class.
67 124
125Many watchers either are used with "recursion" (repeating timers for
126example), or need to refer to their watcher object in other ways.
127
128An any way to achieve that is this pattern:
129
130 my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
131 # you can use $w here, for example to undef it
132 undef $w;
133 });
134
135Note that C<my $w; $w => combination. This is necessary because in Perl,
136my variables are only visible after the statement in which they are
137declared.
138
68=head2 IO WATCHERS 139=head2 IO WATCHERS
69 140
70You can create I/O watcher by calling the C<< AnyEvent->io >> method with 141You can create an I/O watcher by calling the C<< AnyEvent->io >> method
71the following mandatory arguments: 142with the following mandatory key-value pairs as arguments:
72 143
73C<fh> the Perl I<filehandle> (not filedescriptor) to watch for 144C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for
74events. C<poll> must be a string that is either C<r> or C<w>, that creates 145events. C<poll> must be a string that is either C<r> or C<w>, which
75a watcher waiting for "r"eadable or "w"ritable events. C<cb> teh callback 146creates a watcher waiting for "r"eadable or "w"ritable events,
76to invoke everytime the filehandle becomes ready. 147respectively. C<cb> is the callback to invoke each time the file handle
148becomes ready.
77 149
78Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on
79a socket you can have one r + one w, not any more (limitation comes from
80Tk - if you are sure you are not using Tk this limitation is gone).
81
82Filehandles will be kept alive, so as long as the watcher exists, the 150File handles will be kept alive, so as long as the watcher exists, the
83filehandle exists, too. 151file handle exists, too.
152
153It is not allowed to close a file handle as long as any watcher is active
154on the underlying file descriptor.
155
156Some event loops issue spurious readyness notifications, so you should
157always use non-blocking calls when reading/writing from/to your file
158handles.
84 159
85Example: 160Example:
86 161
87 # wait for readability of STDIN, then read a line and disable the watcher 162 # wait for readability of STDIN, then read a line and disable the watcher
88 my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { 163 my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
… …
94=head2 TIME WATCHERS 169=head2 TIME WATCHERS
95 170
96You can create a time watcher by calling the C<< AnyEvent->timer >> 171You can create a time watcher by calling the C<< AnyEvent->timer >>
97method with the following mandatory arguments: 172method with the following mandatory arguments:
98 173
99C<after> after how many seconds (fractions are supported) should the timer 174C<after> specifies after how many seconds (fractional values are
100activate. C<cb> the callback to invoke. 175supported) should the timer activate. C<cb> the callback to invoke in that
176case.
101 177
102The timer callback will be invoked at most once: if you want a repeating 178The timer callback will be invoked at most once: if you want a repeating
103timer you have to create a new watcher (this is a limitation by both Tk 179timer you have to create a new watcher (this is a limitation by both Tk
104and Glib). 180and Glib).
105 181
… …
109 my $w = AnyEvent->timer (after => 7.7, cb => sub { 185 my $w = AnyEvent->timer (after => 7.7, cb => sub {
110 warn "timeout\n"; 186 warn "timeout\n";
111 }); 187 });
112 188
113 # to cancel the timer: 189 # to cancel the timer:
114 undef $w 190 undef $w;
115 191
192Example 2:
193
194 # fire an event after 0.5 seconds, then roughly every second
195 my $w;
196
197 my $cb = sub {
198 # cancel the old timer while creating a new one
199 $w = AnyEvent->timer (after => 1, cb => $cb);
200 };
201
202 # start the "loop" by creating the first watcher
203 $w = AnyEvent->timer (after => 0.5, cb => $cb);
204
205=head3 TIMING ISSUES
206
207There are two ways to handle timers: based on real time (relative, "fire
208in 10 seconds") and based on wallclock time (absolute, "fire at 12
209o'clock").
210
211While most event loops expect timers to specified in a relative way, they use
212absolute time internally. This makes a difference when your clock "jumps",
213for example, when ntp decides to set your clock backwards from the wrong 2014-01-01 to
2142008-01-01, a watcher that you created to fire "after" a second might actually take
215six years to finally fire.
216
217AnyEvent cannot compensate for this. The only event loop that is conscious
218about these issues is L<EV>, which offers both relative (ev_timer) and
219absolute (ev_periodic) timers.
220
221AnyEvent always prefers relative timers, if available, matching the
222AnyEvent API.
223
224=head2 SIGNAL WATCHERS
225
226You can watch for signals using a signal watcher, C<signal> is the signal
227I<name> without any C<SIG> prefix, C<cb> is the Perl callback to
228be invoked whenever a signal occurs.
229
230Multiple signals occurances can be clumped together into one callback
231invocation, and callback invocation will be synchronous. synchronous means
232that it might take a while until the signal gets handled by the process,
233but it is guarenteed not to interrupt any other callbacks.
234
235The main advantage of using these watchers is that you can share a signal
236between multiple watchers.
237
238This watcher might use C<%SIG>, so programs overwriting those signals
239directly will likely not work correctly.
240
241Example: exit on SIGINT
242
243 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
244
245=head2 CHILD PROCESS WATCHERS
246
247You can also watch on a child process exit and catch its exit status.
248
249The child process is specified by the C<pid> argument (if set to C<0>, it
250watches for any child process exit). The watcher will trigger as often
251as status change for the child are received. This works by installing a
252signal handler for C<SIGCHLD>. The callback will be called with the pid
253and exit status (as returned by waitpid).
254
255Example: wait for pid 1333
256
257 my $w = AnyEvent->child (
258 pid => 1333,
259 cb => sub {
260 my ($pid, $status) = @_;
261 warn "pid $pid exited with status $status";
262 },
263 );
264
116=head2 CONDITION WATCHERS 265=head2 CONDITION VARIABLES
117 266
118Condition watchers can be created by calling the C<< AnyEvent->condvar >> 267Condition variables can be created by calling the C<< AnyEvent->condvar >>
119method without any arguments. 268method without any arguments.
120 269
121A condition watcher watches for a condition - precisely that the C<< 270A condition variable waits for a condition - precisely that the C<<
122->broadcast >> method has been called. 271->broadcast >> method has been called.
123 272
124The watcher has only two methods: 273They are very useful to signal that a condition has been fulfilled, for
274example, if you write a module that does asynchronous http requests,
275then a condition variable would be the ideal candidate to signal the
276availability of results.
277
278You can also use condition variables to block your main program until
279an event occurs - for example, you could C<< ->wait >> in your main
280program until the user clicks the Quit button in your app, which would C<<
281->broadcast >> the "quit" event.
282
283Note that condition variables recurse into the event loop - if you have
284two pirces of code that call C<< ->wait >> in a round-robbin fashion, you
285lose. Therefore, condition variables are good to export to your caller, but
286you should avoid making a blocking wait yourself, at least in callbacks,
287as this asks for trouble.
288
289This object has two methods:
125 290
126=over 4 291=over 4
127 292
128=item $cv->wait 293=item $cv->wait
129 294
130Wait (blocking if necessary) until the C<< ->broadcast >> method has been 295Wait (blocking if necessary) until the C<< ->broadcast >> method has been
131called on c<$cv>, while servicing other watchers normally. 296called on c<$cv>, while servicing other watchers normally.
132 297
133Not all event models support a blocking wait - some die in that case, so
134if you are using this from a module, never require a blocking wait, but
135let the caller decide wether the call will block or not (for example,
136by coupling condition variables with some kind of request results and
137supporting callbacks so the caller knows that getting the result will not
138block, while still suppporting blockign waits if the caller so desires).
139
140You can only wait once on a condition - additional calls will return 298You can only wait once on a condition - additional calls will return
141immediately. 299immediately.
142 300
301Not all event models support a blocking wait - some die in that case
302(programs might want to do that to stay interactive), so I<if you are
303using this from a module, never require a blocking wait>, but let the
304caller decide whether the call will block or not (for example, by coupling
305condition variables with some kind of request results and supporting
306callbacks so the caller knows that getting the result will not block,
307while still suppporting blocking waits if the caller so desires).
308
309Another reason I<never> to C<< ->wait >> in a module is that you cannot
310sensibly have two C<< ->wait >>'s in parallel, as that would require
311multiple interpreters or coroutines/threads, none of which C<AnyEvent>
312can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and
313L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s
314from different coroutines, however).
315
143=item $cv->broadcast 316=item $cv->broadcast
144 317
145Flag the condition as ready - a running C<< ->wait >> and all further 318Flag the condition as ready - a running C<< ->wait >> and all further
146calls to C<wait> will return after this method has been called. If nobody 319calls to C<wait> will (eventually) return after this method has been
147is waiting the broadcast will be remembered.. 320called. If nobody is waiting the broadcast will be remembered..
321
322=back
148 323
149Example: 324Example:
150 325
151 # wait till the result is ready 326 # wait till the result is ready
152 my $result_ready = AnyEvent->condvar; 327 my $result_ready = AnyEvent->condvar;
153 328
154 # do something such as adding a timer 329 # do something such as adding a timer
155 # or socket watcher the calls $result_ready->broadcast 330 # or socket watcher the calls $result_ready->broadcast
156 # when the "result" is ready. 331 # when the "result" is ready.
332 # in this case, we simply use a timer:
333 my $w = AnyEvent->timer (
334 after => 1,
335 cb => sub { $result_ready->broadcast },
336 );
157 337
338 # this "blocks" (while handling events) till the watcher
339 # calls broadcast
158 $result_ready->wait; 340 $result_ready->wait;
159 341
160=back 342=head1 GLOBAL VARIABLES AND FUNCTIONS
161
162=head2 SIGNAL WATCHERS
163
164You can listen for signals using a signal watcher, C<signal> is the signal
165I<name> without any C<SIG> prefix. Multiple signals events can be clumped
166together into one callback invocation, and callback invocation might or
167might not be asynchronous.
168
169These watchers might use C<%SIG>, so programs overwriting those signals
170directly will likely not work correctly.
171
172Example: exit on SIGINT
173
174 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
175
176=head2 CHILD PROCESS WATCHERS
177
178You can also listen for the status of a child process specified by the
179C<pid> argument. The watcher will only trigger once. This works by
180installing a signal handler for C<SIGCHLD>.
181
182Example: wait for pid 1333
183
184 my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
185
186=head1 GLOBALS
187 343
188=over 4 344=over 4
189 345
190=item $AnyEvent::MODEL 346=item $AnyEvent::MODEL
191 347
… …
195C<AnyEvent::Impl:xxx> modules, but can be any other class in the case 351C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
196AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). 352AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
197 353
198The known classes so far are: 354The known classes so far are:
199 355
200 EV::AnyEvent based on EV (an interface to libev, best choice) 356 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
201 AnyEvent::Impl::Coro based on Coro::Event, second best choice. 357 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
358 AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
202 AnyEvent::Impl::Event based on Event, also second best choice :) 359 AnyEvent::Impl::Event based on Event, also second best choice :)
203 AnyEvent::Impl::Glib based on Glib, second-best choice. 360 AnyEvent::Impl::Glib based on Glib, third-best choice.
204 AnyEvent::Impl::Tk based on Tk, very bad choice. 361 AnyEvent::Impl::Tk based on Tk, very bad choice.
205 AnyEvent::Impl::Perl pure-perl implementation, inefficient. 362 AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
206 363
207=item AnyEvent::detect 364=item AnyEvent::detect
208 365
209Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if 366Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
210necessary. You should only call this function right before you would have 367if necessary. You should only call this function right before you would
211created an AnyEvent watcher anyway, that is, very late at runtime. 368have created an AnyEvent watcher anyway, that is, as late as possible at
369runtime.
212 370
213=back 371=back
214 372
215=head1 WHAT TO DO IN A MODULE 373=head1 WHAT TO DO IN A MODULE
216 374
217As a module author, you should "use AnyEvent" and call AnyEvent methods 375As a module author, you should C<use AnyEvent> and call AnyEvent methods
218freely, but you should not load a specific event module or rely on it. 376freely, but you should not load a specific event module or rely on it.
219 377
220Be careful when you create watchers in the module body - Anyevent will 378Be careful when you create watchers in the module body - AnyEvent will
221decide which event module to use as soon as the first method is called, so 379decide which event module to use as soon as the first method is called, so
222by calling AnyEvent in your module body you force the user of your module 380by calling AnyEvent in your module body you force the user of your module
223to load the event module first. 381to load the event module first.
224 382
383Never call C<< ->wait >> on a condition variable unless you I<know> that
384the C<< ->broadcast >> method has been called on it already. This is
385because it will stall the whole program, and the whole point of using
386events is to stay interactive.
387
388It is fine, however, to call C<< ->wait >> when the user of your module
389requests it (i.e. if you create a http request object ad have a method
390called C<results> that returns the results, it should call C<< ->wait >>
391freely, as the user of your module knows what she is doing. always).
392
225=head1 WHAT TO DO IN THE MAIN PROGRAM 393=head1 WHAT TO DO IN THE MAIN PROGRAM
226 394
227There will always be a single main program - the only place that should 395There will always be a single main program - the only place that should
228dictate which event model to use. 396dictate which event model to use.
229 397
230If it doesn't care, it can just "use AnyEvent" and use it itself, or not 398If it doesn't care, it can just "use AnyEvent" and use it itself, or not
231do anything special and let AnyEvent decide which implementation to chose. 399do anything special (it does not need to be event-based) and let AnyEvent
400decide which implementation to chose if some module relies on it.
232 401
233If the main program relies on a specific event model (for example, in Gtk2 402If the main program relies on a specific event model. For example, in
234programs you have to rely on either Glib or Glib::Event), you should load 403Gtk2 programs you have to rely on the Glib module. You should load the
235it before loading AnyEvent or any module that uses it, generally, as early 404event module before loading AnyEvent or any module that uses it: generally
236as possible. The reason is that modules might create watchers when they 405speaking, you should load it as early as possible. The reason is that
237are loaded, and AnyEvent will decide on the event model to use as soon as 406modules might create watchers when they are loaded, and AnyEvent will
238it creates watchers, and it might chose the wrong one unless you load the 407decide on the event model to use as soon as it creates watchers, and it
239correct one yourself. 408might chose the wrong one unless you load the correct one yourself.
240 409
241You can chose to use a rather inefficient pure-perl implementation by 410You can chose to use a rather inefficient pure-perl implementation by
242loading the C<AnyEvent::Impl::Perl> module, but letting AnyEvent chose is 411loading the C<AnyEvent::Impl::Perl> module, which gives you similar
243generally better. 412behaviour everywhere, but letting AnyEvent chose is generally better.
244 413
245=cut 414=cut
246 415
247package AnyEvent; 416package AnyEvent;
248 417
249no warnings; 418no warnings;
250use strict; 419use strict;
251 420
252use Carp; 421use Carp;
253 422
254our $VERSION = '2.55'; 423our $VERSION = '3.12';
255our $MODEL; 424our $MODEL;
256 425
257our $AUTOLOAD; 426our $AUTOLOAD;
258our @ISA; 427our @ISA;
259 428
260our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 429our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
261 430
262our @REGISTRY; 431our @REGISTRY;
263 432
264my @models = ( 433my @models = (
434 [Coro::EV:: => AnyEvent::Impl::CoroEV::],
265 [Coro::Event:: => AnyEvent::Impl::Coro::], 435 [Coro::Event:: => AnyEvent::Impl::CoroEvent::],
266 [EV:: => EV::AnyEvent::], 436 [EV:: => AnyEvent::Impl::EV::],
267 [Event:: => AnyEvent::Impl::Event::], 437 [Event:: => AnyEvent::Impl::Event::],
268 [Glib:: => AnyEvent::Impl::Glib::], 438 [Glib:: => AnyEvent::Impl::Glib::],
269 [Tk:: => AnyEvent::Impl::Tk::], 439 [Tk:: => AnyEvent::Impl::Tk::],
270 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 440 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
271); 441);
… …
301 last; 471 last;
302 } 472 }
303 } 473 }
304 474
305 $MODEL 475 $MODEL
306 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: Event (or Coro+Event), Glib or Tk."; 476 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event), Glib or Tk.";
307 } 477 }
308 478
309 unshift @ISA, $MODEL; 479 unshift @ISA, $MODEL;
310 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 480 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
311 } 481 }
… …
369 539
370# default implementation for ->child 540# default implementation for ->child
371 541
372our %PID_CB; 542our %PID_CB;
373our $CHLD_W; 543our $CHLD_W;
544our $CHLD_DELAY_W;
374our $PID_IDLE; 545our $PID_IDLE;
375our $WNOHANG; 546our $WNOHANG;
376 547
377sub _child_wait { 548sub _child_wait {
378 while (0 < (my $pid = waitpid -1, $WNOHANG)) { 549 while (0 < (my $pid = waitpid -1, $WNOHANG)) {
379 $_->() for values %{ (delete $PID_CB{$pid}) || {} }; 550 $_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),
551 (values %{ $PID_CB{0} || {} });
380 } 552 }
381 553
382 undef $PID_IDLE; 554 undef $PID_IDLE;
555}
556
557sub _sigchld {
558 # make sure we deliver these changes "synchronous" with the event loop.
559 $CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
560 undef $CHLD_DELAY_W;
561 &_child_wait;
562 });
383} 563}
384 564
385sub child { 565sub child {
386 my (undef, %arg) = @_; 566 my (undef, %arg) = @_;
387 567
388 my $pid = uc $arg{pid} 568 defined (my $pid = $arg{pid} + 0)
389 or Carp::croak "required option 'pid' is missing"; 569 or Carp::croak "required option 'pid' is missing";
390 570
391 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 571 $PID_CB{$pid}{$arg{cb}} = $arg{cb};
392 572
393 unless ($WNOHANG) { 573 unless ($WNOHANG) {
394 $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1; 574 $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1;
395 } 575 }
396 576
397 unless ($CHLD_W) { 577 unless ($CHLD_W) {
398 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_child_wait); 578 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
399 # child could be a zombie already 579 # child could be a zombie already, so make at least one round
400 $PID_IDLE ||= AnyEvent->timer (after => 0, cb => \&_child_wait); 580 &_sigchld;
401 } 581 }
402 582
403 bless [$pid, $arg{cb}], "AnyEvent::Base::Child" 583 bless [$pid, $arg{cb}], "AnyEvent::Base::Child"
404} 584}
405 585
… …
411 591
412 undef $CHLD_W unless keys %PID_CB; 592 undef $CHLD_W unless keys %PID_CB;
413} 593}
414 594
415=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 595=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
596
597This is an advanced topic that you do not normally need to use AnyEvent in
598a module. This section is only of use to event loop authors who want to
599provide AnyEvent compatibility.
416 600
417If you need to support another event library which isn't directly 601If you need to support another event library which isn't directly
418supported by AnyEvent, you can supply your own interface to it by 602supported by AnyEvent, you can supply your own interface to it by
419pushing, before the first watcher gets created, the package name of 603pushing, before the first watcher gets created, the package name of
420the event module and the package name of the interface to use onto 604the event module and the package name of the interface to use onto
421C<@AnyEvent::REGISTRY>. You can do that before and even without loading 605C<@AnyEvent::REGISTRY>. You can do that before and even without loading
422AnyEvent. 606AnyEvent, so it is reasonably cheap.
423 607
424Example: 608Example:
425 609
426 push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::]; 610 push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];
427 611
428This tells AnyEvent to (literally) use the C<urxvt::anyevent::> 612This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
429package/class when it finds the C<urxvt> package/module is loaded. When 613package/class when it finds the C<urxvt> package/module is already loaded.
614
430AnyEvent is loaded and asked to find a suitable event model, it will 615When AnyEvent is loaded and asked to find a suitable event model, it
431first check for the presence of urxvt. 616will first check for the presence of urxvt by trying to C<use> the
617C<urxvt::anyevent> module.
432 618
433The class should provide implementations for all watcher types (see 619The class should provide implementations for all watcher types. See
434L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib> 620L<AnyEvent::Impl::EV> (source code), L<AnyEvent::Impl::Glib> (Source code)
435(Source code) and so on for actual examples, use C<perldoc -m 621and so on for actual examples. Use C<perldoc -m AnyEvent::Impl::Glib> to
436AnyEvent::Impl::Glib> to see the sources). 622see the sources.
437 623
624If you don't provide C<signal> and C<child> watchers than AnyEvent will
625provide suitable (hopefully) replacements.
626
438The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt) 627The above example isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
439uses the above line as-is. An interface isn't included in AnyEvent 628terminal emulator uses the above line as-is. An interface isn't included
440because it doesn't make sense outside the embedded interpreter inside 629in AnyEvent because it doesn't make sense outside the embedded interpreter
441I<rxvt-unicode>, and it is updated and maintained as part of the 630inside I<rxvt-unicode>, and it is updated and maintained as part of the
442I<rxvt-unicode> distribution. 631I<rxvt-unicode> distribution.
443 632
444I<rxvt-unicode> also cheats a bit by not providing blocking access to 633I<rxvt-unicode> also cheats a bit by not providing blocking access to
445condition variables: code blocking while waiting for a condition will 634condition variables: code blocking while waiting for a condition will
446C<die>. This still works with most modules/usages, and blocking calls must 635C<die>. This still works with most modules/usages, and blocking calls must
447not be in an interactive application, so it makes sense. 636not be done in an interactive application, so it makes sense.
448 637
449=head1 ENVIRONMENT VARIABLES 638=head1 ENVIRONMENT VARIABLES
450 639
451The following environment variables are used by this module: 640The following environment variables are used by this module:
452 641
453C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, reports which event 642C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, cause AnyEvent to
454model gets used. 643report to STDERR which event model it chooses.
455 644
456=head1 EXAMPLE 645=head1 EXAMPLE PROGRAM
457 646
458The following program uses an io watcher to read data from stdin, a timer 647The following program uses an IO watcher to read data from STDIN, a timer
459to display a message once per second, and a condvar to exit the program 648to display a message once per second, and a condition variable to quit the
460when the user enters quit: 649program when the user enters quit:
461 650
462 use AnyEvent; 651 use AnyEvent;
463 652
464 my $cv = AnyEvent->condvar; 653 my $cv = AnyEvent->condvar;
465 654
466 my $io_watcher = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { 655 my $io_watcher = AnyEvent->io (
656 fh => \*STDIN,
657 poll => 'r',
658 cb => sub {
467 warn "io event <$_[0]>\n"; # will always output <r> 659 warn "io event <$_[0]>\n"; # will always output <r>
468 chomp (my $input = <STDIN>); # read a line 660 chomp (my $input = <STDIN>); # read a line
469 warn "read: $input\n"; # output what has been read 661 warn "read: $input\n"; # output what has been read
470 $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i 662 $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i
663 },
471 }); 664 );
472 665
473 my $time_watcher; # can only be used once 666 my $time_watcher; # can only be used once
474 667
475 sub new_timer { 668 sub new_timer {
476 $timer = AnyEvent->timer (after => 1, cb => sub { 669 $timer = AnyEvent->timer (after => 1, cb => sub {
… …
558 $txn->{finished}->wait; 751 $txn->{finished}->wait;
559 return $txn->{result}; 752 return $txn->{result};
560 753
561The actual code goes further and collects all errors (C<die>s, exceptions) 754The actual code goes further and collects all errors (C<die>s, exceptions)
562that occured during request processing. The C<result> method detects 755that occured during request processing. The C<result> method detects
563wether an exception as thrown (it is stored inside the $txn object) 756whether an exception as thrown (it is stored inside the $txn object)
564and just throws the exception, which means connection errors and other 757and just throws the exception, which means connection errors and other
565problems get reported tot he code that tries to use the result, not in a 758problems get reported tot he code that tries to use the result, not in a
566random callback. 759random callback.
567 760
568All of this enables the following usage styles: 761All of this enables the following usage styles:
569 762
5701. Blocking: 7631. Blocking:
571 764
572 my $data = $fcp->client_get ($url); 765 my $data = $fcp->client_get ($url);
573 766
5742. Blocking, but parallelizing: 7672. Blocking, but running in parallel:
575 768
576 my @datas = map $_->result, 769 my @datas = map $_->result,
577 map $fcp->txn_client_get ($_), 770 map $fcp->txn_client_get ($_),
578 @urls; 771 @urls;
579 772
580Both blocking examples work without the module user having to know 773Both blocking examples work without the module user having to know
581anything about events. 774anything about events.
582 775
5833a. Event-based in a main program, using any support Event module: 7763a. Event-based in a main program, using any supported event module:
584 777
585 use Event; 778 use EV;
586 779
587 $fcp->txn_client_get ($url)->cb (sub { 780 $fcp->txn_client_get ($url)->cb (sub {
588 my $txn = shift; 781 my $txn = shift;
589 my $data = $txn->result; 782 my $data = $txn->result;
590 ... 783 ...
591 }); 784 });
592 785
593 Event::loop; 786 EV::loop;
594 787
5953b. The module user could use AnyEvent, too: 7883b. The module user could use AnyEvent, too:
596 789
597 use AnyEvent; 790 use AnyEvent;
598 791
… …
605 798
606 $quit->wait; 799 $quit->wait;
607 800
608=head1 SEE ALSO 801=head1 SEE ALSO
609 802
610Event modules: L<Coro::Event>, L<Coro>, L<Event>, L<Glib::Event>, L<Glib>. 803Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>,
804L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>.
611 805
612Implementations: L<AnyEvent::Impl::Coro>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>. 806Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>,
807L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>,
808L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>.
613 809
614Nontrivial usage example: L<Net::FCP>. 810Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.
615 811
616=head1 812=head1 AUTHOR
813
814 Marc Lehmann <schmorp@schmorp.de>
815 http://home.schmorp.de/
617 816
618=cut 817=cut
619 818
6201 8191
621 820

Diff Legend

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