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.17 by root, Fri Nov 24 14:40:13 2006 UTC vs.
Revision 1.42 by root, Mon Apr 7 19:40:12 2008 UTC

17 }); 17 });
18 18
19 my $w = AnyEvent->condvar; # stores wether a condition was flagged 19 my $w = AnyEvent->condvar; # stores wether 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
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, and AnyEvent
35helps hiding the differences.
36
37The goal of AnyEvent is to offer module authors the ability to do event
38programming (waiting for I/O or timer events) without subscribing to a
39religion, a way of living, and most importantly: without forcing your
40module users into the same thing by forcing them to use the same event
41model you use.
42
43For modules like POE or IO::Async (which is actually doing all I/O
44I<synchronously>...), using them in your module is like joining a
45cult: After you joined, you are dependent on them and you cannot use
46anything else, as it is simply incompatible to everything that isn't
47itself.
48
49AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk
50works fine etc. etc. but none of these work together with the rest: POE
51+ IO::Async? no go. Tk + Event? no go. If your module uses one of
52those, every user of your module has to use it, too. If your module
53uses AnyEvent, it works transparently with all event models it supports
54(including stuff like POE and IO::Async).
55
56In addition of being free of having to use I<the one and only true event
57model>, AnyEvent also is free of bloat and policy: with POE or similar
58modules, you get an enourmous amount of code and strict rules you have
59to follow. AnyEvent, on the other hand, is lean and to the point by only
60offering the functionality that is useful, in as thin as a wrapper as
61technically possible.
62
22 63
23=head1 DESCRIPTION 64=head1 DESCRIPTION
24 65
25L<AnyEvent> provides an identical interface to multiple event loops. This 66L<AnyEvent> provides an identical interface to multiple event loops. This
26allows module authors to utilise an event loop without forcing module 67allows module authors to utilise an event loop without forcing module
70You can create I/O watcher by calling the C<< AnyEvent->io >> method with 111You can create I/O watcher by calling the C<< AnyEvent->io >> method with
71the following mandatory arguments: 112the following mandatory arguments:
72 113
73C<fh> the Perl I<filehandle> (not filedescriptor) to watch for 114C<fh> the Perl I<filehandle> (not filedescriptor) to watch for
74events. C<poll> must be a string that is either C<r> or C<w>, that creates 115events. C<poll> must be a string that is either C<r> or C<w>, that creates
75a watcher waiting for "r"eadable or "w"ritable events. C<cb> teh callback 116a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback
76to invoke everytime the filehandle becomes ready. 117to invoke everytime the filehandle becomes ready.
77 118
78Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on 119Only 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 120a 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). 121Tk - if you are sure you are not using Tk this limitation is gone).
89 chomp (my $input = <STDIN>); 130 chomp (my $input = <STDIN>);
90 warn "read: $input\n"; 131 warn "read: $input\n";
91 undef $w; 132 undef $w;
92 }); 133 });
93 134
94=head2 TIMER WATCHERS 135=head2 TIME WATCHERS
95 136
96You can create a timer watcher by calling the C<< AnyEvent->timer >> 137You can create a time watcher by calling the C<< AnyEvent->timer >>
97method with the following mandatory arguments: 138method with the following mandatory arguments:
98 139
99C<after> after how many seconds (fractions are supported) should the timer 140C<after> after how many seconds (fractions are supported) should the timer
100activate. C<cb> the callback to invoke. 141activate. C<cb> the callback to invoke.
101 142
109 my $w = AnyEvent->timer (after => 7.7, cb => sub { 150 my $w = AnyEvent->timer (after => 7.7, cb => sub {
110 warn "timeout\n"; 151 warn "timeout\n";
111 }); 152 });
112 153
113 # to cancel the timer: 154 # to cancel the timer:
114 undef $w 155 undef $w;
115 156
116=head2 CONDITION WATCHERS 157=head2 CONDITION WATCHERS
117 158
118Condition watchers can be created by calling the C<< AnyEvent->condvar >> 159Condition watchers can be created by calling the C<< AnyEvent->condvar >>
119method without any arguments. 160method without any arguments.
120 161
121A condition watcher watches for a condition - precisely that the C<< 162A condition watcher watches for a condition - precisely that the C<<
122->broadcast >> method has been called. 163->broadcast >> method has been called.
164
165Note that condition watchers recurse into the event loop - if you have
166two watchers that call C<< ->wait >> in a round-robbin fashion, you
167lose. Therefore, condition watchers are good to export to your caller, but
168you should avoid making a blocking wait, at least in callbacks, as this
169usually asks for trouble.
123 170
124The watcher has only two methods: 171The watcher has only two methods:
125 172
126=over 4 173=over 4
127 174
157 204
158 $result_ready->wait; 205 $result_ready->wait;
159 206
160=back 207=back
161 208
209=head2 SIGNAL WATCHERS
210
211You can listen for signals using a signal watcher, C<signal> is the signal
212I<name> without any C<SIG> prefix. Multiple signals events can be clumped
213together into one callback invocation, and callback invocation might or
214might not be asynchronous.
215
216These watchers might use C<%SIG>, so programs overwriting those signals
217directly will likely not work correctly.
218
219Example: exit on SIGINT
220
221 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
222
223=head2 CHILD PROCESS WATCHERS
224
225You can also listen for the status of a child process specified by the
226C<pid> argument (or any child if the pid argument is 0). The watcher will
227trigger as often as status change for the child are received. This works
228by installing a signal handler for C<SIGCHLD>. The callback will be called with
229the pid and exit status (as returned by waitpid).
230
231Example: wait for pid 1333
232
233 my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
234
162=head1 GLOBALS 235=head1 GLOBALS
163 236
164=over 4 237=over 4
165 238
166=item $AnyEvent::MODEL 239=item $AnyEvent::MODEL
171C<AnyEvent::Impl:xxx> modules, but can be any other class in the case 244C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
172AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). 245AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
173 246
174The known classes so far are: 247The known classes so far are:
175 248
176 AnyEvent::Impl::Coro based on Coro::Event, best choise. 249 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
250 AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
251 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
177 AnyEvent::Impl::Event based on Event, also best choice :) 252 AnyEvent::Impl::Event based on Event, also second best choice :)
178 AnyEvent::Impl::Glib based on Glib, second-best choice. 253 AnyEvent::Impl::Glib based on Glib, second-best choice.
179 AnyEvent::Impl::Tk based on Tk, very bad choice. 254 AnyEvent::Impl::Tk based on Tk, very bad choice.
180 AnyEvent::Impl::Perl pure-perl implementation, inefficient. 255 AnyEvent::Impl::Perl pure-perl implementation, inefficient.
256
257=item AnyEvent::detect
258
259Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if
260necessary. You should only call this function right before you would have
261created an AnyEvent watcher anyway, that is, very late at runtime.
181 262
182=back 263=back
183 264
184=head1 WHAT TO DO IN A MODULE 265=head1 WHAT TO DO IN A MODULE
185 266
214=cut 295=cut
215 296
216package AnyEvent; 297package AnyEvent;
217 298
218no warnings; 299no warnings;
219use strict 'vars'; 300use strict;
301
220use Carp; 302use Carp;
221 303
222our $VERSION = '2.1'; 304our $VERSION = '3.0';
223our $MODEL; 305our $MODEL;
224 306
225our $AUTOLOAD; 307our $AUTOLOAD;
226our @ISA; 308our @ISA;
227 309
228our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 310our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
229 311
230our @REGISTRY; 312our @REGISTRY;
231 313
232my @models = ( 314my @models = (
315 [Coro::EV:: => AnyEvent::Impl::CoroEV::],
316 [EV:: => AnyEvent::Impl::EV::],
233 [Coro::Event:: => AnyEvent::Impl::Coro::], 317 [Coro::Event:: => AnyEvent::Impl::CoroEvent::],
234 [Event:: => AnyEvent::Impl::Event::], 318 [Event:: => AnyEvent::Impl::Event::],
235 [Glib:: => AnyEvent::Impl::Glib::], 319 [Glib:: => AnyEvent::Impl::Glib::],
236 [Tk:: => AnyEvent::Impl::Tk::], 320 [Tk:: => AnyEvent::Impl::Tk::],
237 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 321 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
238); 322);
239 323
240our %method = map +($_ => 1), qw(io timer condvar broadcast wait DESTROY); 324our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY);
241 325
242sub AUTOLOAD { 326sub detect() {
243 $AUTOLOAD =~ s/.*://;
244
245 $method{$AUTOLOAD}
246 or croak "$AUTOLOAD: not a valid method for AnyEvent objects";
247
248 unless ($MODEL) { 327 unless ($MODEL) {
328 no strict 'refs';
329
249 # check for already loaded models 330 # check for already loaded models
250 for (@REGISTRY, @models) { 331 for (@REGISTRY, @models) {
251 my ($package, $model) = @$_; 332 my ($package, $model) = @$_;
252 if (${"$package\::VERSION"} > 0) { 333 if (${"$package\::VERSION"} > 0) {
253 if (eval "require $model") { 334 if (eval "require $model") {
261 unless ($MODEL) { 342 unless ($MODEL) {
262 # try to load a model 343 # try to load a model
263 344
264 for (@REGISTRY, @models) { 345 for (@REGISTRY, @models) {
265 my ($package, $model) = @$_; 346 my ($package, $model) = @$_;
347 if (eval "require $package"
348 and ${"$package\::VERSION"} > 0
266 if (eval "require $model") { 349 and eval "require $model") {
267 $MODEL = $model; 350 $MODEL = $model;
268 warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1; 351 warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1;
269 last; 352 last;
270 } 353 }
271 } 354 }
272 355
273 $MODEL 356 $MODEL
274 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: Coro, Event, Glib or Tk."; 357 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.";
275 } 358 }
359
360 unshift @ISA, $MODEL;
361 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
276 } 362 }
277 363
278 @ISA = $MODEL; 364 $MODEL
365}
366
367sub AUTOLOAD {
368 (my $func = $AUTOLOAD) =~ s/.*://;
369
370 $method{$func}
371 or croak "$func: not a valid method for AnyEvent objects";
372
373 detect unless $MODEL;
279 374
280 my $class = shift; 375 my $class = shift;
281 $class->$AUTOLOAD (@_); 376 $class->$func (@_);
377}
378
379package AnyEvent::Base;
380
381# default implementation for ->condvar, ->wait, ->broadcast
382
383sub condvar {
384 bless \my $flag, "AnyEvent::Base::CondVar"
385}
386
387sub AnyEvent::Base::CondVar::broadcast {
388 ${$_[0]}++;
389}
390
391sub AnyEvent::Base::CondVar::wait {
392 AnyEvent->one_event while !${$_[0]};
393}
394
395# default implementation for ->signal
396
397our %SIG_CB;
398
399sub signal {
400 my (undef, %arg) = @_;
401
402 my $signal = uc $arg{signal}
403 or Carp::croak "required option 'signal' is missing";
404
405 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
406 $SIG{$signal} ||= sub {
407 $_->() for values %{ $SIG_CB{$signal} || {} };
408 };
409
410 bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"
411}
412
413sub AnyEvent::Base::Signal::DESTROY {
414 my ($signal, $cb) = @{$_[0]};
415
416 delete $SIG_CB{$signal}{$cb};
417
418 $SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };
419}
420
421# default implementation for ->child
422
423our %PID_CB;
424our $CHLD_W;
425our $CHLD_DELAY_W;
426our $PID_IDLE;
427our $WNOHANG;
428
429sub _child_wait {
430 while (0 < (my $pid = waitpid -1, $WNOHANG)) {
431 $_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),
432 (values %{ $PID_CB{0} || {} });
433 }
434
435 undef $PID_IDLE;
436}
437
438sub _sigchld {
439 # make sure we deliver these changes "synchronous" with the event loop.
440 $CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
441 undef $CHLD_DELAY_W;
442 &_child_wait;
443 });
444}
445
446sub child {
447 my (undef, %arg) = @_;
448
449 defined (my $pid = $arg{pid} + 0)
450 or Carp::croak "required option 'pid' is missing";
451
452 $PID_CB{$pid}{$arg{cb}} = $arg{cb};
453
454 unless ($WNOHANG) {
455 $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1;
456 }
457
458 unless ($CHLD_W) {
459 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
460 # child could be a zombie already, so make at least one round
461 &_sigchld;
462 }
463
464 bless [$pid, $arg{cb}], "AnyEvent::Base::Child"
465}
466
467sub AnyEvent::Base::Child::DESTROY {
468 my ($pid, $cb) = @{$_[0]};
469
470 delete $PID_CB{$pid}{$cb};
471 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
472
473 undef $CHLD_W unless keys %PID_CB;
282} 474}
283 475
284=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 476=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
285 477
286If you need to support another event library which isn't directly 478If you need to support another event library which isn't directly
297This tells AnyEvent to (literally) use the C<urxvt::anyevent::> 489This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
298package/class when it finds the C<urxvt> package/module is loaded. When 490package/class when it finds the C<urxvt> package/module is loaded. When
299AnyEvent is loaded and asked to find a suitable event model, it will 491AnyEvent is loaded and asked to find a suitable event model, it will
300first check for the presence of urxvt. 492first check for the presence of urxvt.
301 493
302The class should prove implementations for all watcher types (see 494The class should provide implementations for all watcher types (see
303L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib> 495L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib>
304(Source code) and so on for actual examples, use C<perldoc -m 496(Source code) and so on for actual examples, use C<perldoc -m
305AnyEvent::Impl::Glib> to see the sources). 497AnyEvent::Impl::Glib> to see the sources).
306 498
307The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt) 499The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
311I<rxvt-unicode> distribution. 503I<rxvt-unicode> distribution.
312 504
313I<rxvt-unicode> also cheats a bit by not providing blocking access to 505I<rxvt-unicode> also cheats a bit by not providing blocking access to
314condition variables: code blocking while waiting for a condition will 506condition variables: code blocking while waiting for a condition will
315C<die>. This still works with most modules/usages, and blocking calls must 507C<die>. This still works with most modules/usages, and blocking calls must
316not be in an interactive appliation, so it makes sense. 508not be in an interactive application, so it makes sense.
317 509
318=head1 ENVIRONMENT VARIABLES 510=head1 ENVIRONMENT VARIABLES
319 511
320The following environment variables are used by this module: 512The following environment variables are used by this module:
321 513

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines