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.15 by root, Mon Oct 30 20:55:05 2006 UTC vs.
Revision 1.48 by root, Mon Apr 14 19:00:23 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 (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, 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
63Of course, if you want lots of policy (this can arguably be somewhat
64useful) and you want to force your users to use the one and only event
65model, you should I<not> use this module.
66
22 67
23=head1 DESCRIPTION 68=head1 DESCRIPTION
24 69
25L<AnyEvent> provides an identical interface to multiple event loops. This 70L<AnyEvent> provides an identical interface to multiple event loops. This
26allows module authors to utilise an event loop without forcing module 71allows module authors to utilise an event loop without forcing module
70You can create I/O watcher by calling the C<< AnyEvent->io >> method with 115You can create I/O watcher by calling the C<< AnyEvent->io >> method with
71the following mandatory arguments: 116the following mandatory arguments:
72 117
73C<fh> the Perl I<filehandle> (not filedescriptor) to watch for 118C<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 119events. 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 120a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback
76to invoke everytime the filehandle becomes ready. 121to invoke everytime the filehandle becomes ready.
77 122
78Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on 123Only 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 124a 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). 125Tk - if you are sure you are not using Tk this limitation is gone).
89 chomp (my $input = <STDIN>); 134 chomp (my $input = <STDIN>);
90 warn "read: $input\n"; 135 warn "read: $input\n";
91 undef $w; 136 undef $w;
92 }); 137 });
93 138
94=head2 TIMER WATCHERS 139=head2 TIME WATCHERS
95 140
96You can create a timer watcher by calling the C<< AnyEvent->timer >> 141You can create a time watcher by calling the C<< AnyEvent->timer >>
97method with the following mandatory arguments: 142method with the following mandatory arguments:
98 143
99C<after> after how many seconds (fractions are supported) should the timer 144C<after> after how many seconds (fractions are supported) should the timer
100activate. C<cb> the callback to invoke. 145activate. C<cb> the callback to invoke.
101 146
109 my $w = AnyEvent->timer (after => 7.7, cb => sub { 154 my $w = AnyEvent->timer (after => 7.7, cb => sub {
110 warn "timeout\n"; 155 warn "timeout\n";
111 }); 156 });
112 157
113 # to cancel the timer: 158 # to cancel the timer:
114 undef $w 159 undef $w;
115 160
116=head2 CONDITION WATCHERS 161=head2 CONDITION WATCHERS
117 162
118Condition watchers can be created by calling the C<< AnyEvent->condvar >> 163Condition watchers can be created by calling the C<< AnyEvent->condvar >>
119method without any arguments. 164method without any arguments.
120 165
121A condition watcher watches for a condition - precisely that the C<< 166A condition watcher watches for a condition - precisely that the C<<
122->broadcast >> method has been called. 167->broadcast >> method has been called.
123 168
169Note that condition watchers recurse into the event loop - if you have
170two watchers that call C<< ->wait >> in a round-robbin fashion, you
171lose. Therefore, condition watchers are good to export to your caller, but
172you should avoid making a blocking wait, at least in callbacks, as this
173usually asks for trouble.
174
124The watcher has only two methods: 175The watcher has only two methods:
125 176
126=over 4 177=over 4
127 178
128=item $cv->wait 179=item $cv->wait
129 180
130Wait (blocking if necessary) until the C<< ->broadcast >> method has been 181Wait (blocking if necessary) until the C<< ->broadcast >> method has been
131called on c<$cv>, while servicing other watchers normally. 182called on c<$cv>, while servicing other watchers normally.
132 183
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 184You can only wait once on a condition - additional calls will return
141immediately. 185immediately.
186
187Not all event models support a blocking wait - some die in that case
188(programs might want to do that so they stay interactive), so I<if you
189are using this from a module, never require a blocking wait>, but let the
190caller decide wether the call will block or not (for example, by coupling
191condition variables with some kind of request results and supporting
192callbacks so the caller knows that getting the result will not block,
193while still suppporting blocking waits if the caller so desires).
194
195Another reason I<never> to C<< ->wait >> in a module is that you cannot
196sensibly have two C<< ->wait >>'s in parallel, as that would require
197multiple interpreters or coroutines/threads, none of which C<AnyEvent>
198can supply (the coroutine-aware backends C<Coro::EV> and C<Coro::Event>
199explicitly support concurrent C<< ->wait >>'s from different coroutines,
200however).
142 201
143=item $cv->broadcast 202=item $cv->broadcast
144 203
145Flag the condition as ready - a running C<< ->wait >> and all further 204Flag 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 205calls to C<wait> will return after this method has been called. If nobody
154 # do something such as adding a timer 213 # do something such as adding a timer
155 # or socket watcher the calls $result_ready->broadcast 214 # or socket watcher the calls $result_ready->broadcast
156 # when the "result" is ready. 215 # when the "result" is ready.
157 216
158 $result_ready->wait; 217 $result_ready->wait;
218
219=back
220
221=head2 SIGNAL WATCHERS
222
223You can listen for signals using a signal watcher, C<signal> is the signal
224I<name> without any C<SIG> prefix. Multiple signals events can be clumped
225together into one callback invocation, and callback invocation might or
226might not be asynchronous.
227
228These watchers might use C<%SIG>, so programs overwriting those signals
229directly will likely not work correctly.
230
231Example: exit on SIGINT
232
233 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
234
235=head2 CHILD PROCESS WATCHERS
236
237You can also listen for the status of a child process specified by the
238C<pid> argument (or any child if the pid argument is 0). The watcher will
239trigger as often as status change for the child are received. This works
240by installing a signal handler for C<SIGCHLD>. The callback will be called with
241the pid and exit status (as returned by waitpid).
242
243Example: wait for pid 1333
244
245 my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
246
247=head1 GLOBALS
248
249=over 4
250
251=item $AnyEvent::MODEL
252
253Contains C<undef> until the first watcher is being created. Then it
254contains the event model that is being used, which is the name of the
255Perl class implementing the model. This class is usually one of the
256C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
257AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
258
259The known classes so far are:
260
261 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
262 AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
263 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
264 AnyEvent::Impl::Event based on Event, also second best choice :)
265 AnyEvent::Impl::Glib based on Glib, third-best choice.
266 AnyEvent::Impl::Tk based on Tk, very bad choice.
267 AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
268
269=item AnyEvent::detect
270
271Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if
272necessary. You should only call this function right before you would have
273created an AnyEvent watcher anyway, that is, very late at runtime.
159 274
160=back 275=back
161 276
162=head1 WHAT TO DO IN A MODULE 277=head1 WHAT TO DO IN A MODULE
163 278
192=cut 307=cut
193 308
194package AnyEvent; 309package AnyEvent;
195 310
196no warnings; 311no warnings;
197use strict 'vars'; 312use strict;
313
198use Carp; 314use Carp;
199 315
200our $VERSION = '2.0'; 316our $VERSION = '3.0';
201our $MODEL; 317our $MODEL;
202 318
203our $AUTOLOAD; 319our $AUTOLOAD;
204our @ISA; 320our @ISA;
205 321
206our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 322our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
207 323
208our @REGISTRY; 324our @REGISTRY;
209 325
210my @models = ( 326my @models = (
327 [Coro::EV:: => AnyEvent::Impl::CoroEV::],
328 [EV:: => AnyEvent::Impl::EV::],
211 [Coro::Event:: => AnyEvent::Impl::Coro::], 329 [Coro::Event:: => AnyEvent::Impl::CoroEvent::],
212 [Event:: => AnyEvent::Impl::Event::], 330 [Event:: => AnyEvent::Impl::Event::],
213 [Glib:: => AnyEvent::Impl::Glib::], 331 [Glib:: => AnyEvent::Impl::Glib::],
214 [Tk:: => AnyEvent::Impl::Tk::], 332 [Tk:: => AnyEvent::Impl::Tk::],
215 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], 333 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
216); 334);
217 335
218our %method = map +($_ => 1), qw(io timer condvar broadcast wait DESTROY); 336our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY);
219 337
220sub AUTOLOAD { 338sub detect() {
221 $AUTOLOAD =~ s/.*://;
222
223 $method{$AUTOLOAD}
224 or croak "$AUTOLOAD: not a valid method for AnyEvent objects";
225
226 unless ($MODEL) { 339 unless ($MODEL) {
340 no strict 'refs';
341
227 # check for already loaded models 342 # check for already loaded models
228 for (@REGISTRY, @models) { 343 for (@REGISTRY, @models) {
229 my ($package, $model) = @$_; 344 my ($package, $model) = @$_;
230 if (${"$package\::VERSION"} > 0) { 345 if (${"$package\::VERSION"} > 0) {
231 if (eval "require $model") { 346 if (eval "require $model") {
239 unless ($MODEL) { 354 unless ($MODEL) {
240 # try to load a model 355 # try to load a model
241 356
242 for (@REGISTRY, @models) { 357 for (@REGISTRY, @models) {
243 my ($package, $model) = @$_; 358 my ($package, $model) = @$_;
359 if (eval "require $package"
360 and ${"$package\::VERSION"} > 0
244 if (eval "require $model") { 361 and eval "require $model") {
245 $MODEL = $model; 362 $MODEL = $model;
246 warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1; 363 warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1;
247 last; 364 last;
248 } 365 }
249 } 366 }
250 367
251 $MODEL 368 $MODEL
252 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: Coro, Event, Glib or Tk."; 369 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.";
253 } 370 }
371
372 unshift @ISA, $MODEL;
373 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
254 } 374 }
255 375
256 @ISA = $MODEL; 376 $MODEL
377}
378
379sub AUTOLOAD {
380 (my $func = $AUTOLOAD) =~ s/.*://;
381
382 $method{$func}
383 or croak "$func: not a valid method for AnyEvent objects";
384
385 detect unless $MODEL;
257 386
258 my $class = shift; 387 my $class = shift;
259 $class->$AUTOLOAD (@_); 388 $class->$func (@_);
389}
390
391package AnyEvent::Base;
392
393# default implementation for ->condvar, ->wait, ->broadcast
394
395sub condvar {
396 bless \my $flag, "AnyEvent::Base::CondVar"
397}
398
399sub AnyEvent::Base::CondVar::broadcast {
400 ${$_[0]}++;
401}
402
403sub AnyEvent::Base::CondVar::wait {
404 AnyEvent->one_event while !${$_[0]};
405}
406
407# default implementation for ->signal
408
409our %SIG_CB;
410
411sub signal {
412 my (undef, %arg) = @_;
413
414 my $signal = uc $arg{signal}
415 or Carp::croak "required option 'signal' is missing";
416
417 $SIG_CB{$signal}{$arg{cb}} = $arg{cb};
418 $SIG{$signal} ||= sub {
419 $_->() for values %{ $SIG_CB{$signal} || {} };
420 };
421
422 bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"
423}
424
425sub AnyEvent::Base::Signal::DESTROY {
426 my ($signal, $cb) = @{$_[0]};
427
428 delete $SIG_CB{$signal}{$cb};
429
430 $SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };
431}
432
433# default implementation for ->child
434
435our %PID_CB;
436our $CHLD_W;
437our $CHLD_DELAY_W;
438our $PID_IDLE;
439our $WNOHANG;
440
441sub _child_wait {
442 while (0 < (my $pid = waitpid -1, $WNOHANG)) {
443 $_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),
444 (values %{ $PID_CB{0} || {} });
445 }
446
447 undef $PID_IDLE;
448}
449
450sub _sigchld {
451 # make sure we deliver these changes "synchronous" with the event loop.
452 $CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
453 undef $CHLD_DELAY_W;
454 &_child_wait;
455 });
456}
457
458sub child {
459 my (undef, %arg) = @_;
460
461 defined (my $pid = $arg{pid} + 0)
462 or Carp::croak "required option 'pid' is missing";
463
464 $PID_CB{$pid}{$arg{cb}} = $arg{cb};
465
466 unless ($WNOHANG) {
467 $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1;
468 }
469
470 unless ($CHLD_W) {
471 $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
472 # child could be a zombie already, so make at least one round
473 &_sigchld;
474 }
475
476 bless [$pid, $arg{cb}], "AnyEvent::Base::Child"
477}
478
479sub AnyEvent::Base::Child::DESTROY {
480 my ($pid, $cb) = @{$_[0]};
481
482 delete $PID_CB{$pid}{$cb};
483 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
484
485 undef $CHLD_W unless keys %PID_CB;
260} 486}
261 487
262=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 488=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
263 489
264If you need to support another event library which isn't directly 490If you need to support another event library which isn't directly
275This tells AnyEvent to (literally) use the C<urxvt::anyevent::> 501This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
276package/class when it finds the C<urxvt> package/module is loaded. When 502package/class when it finds the C<urxvt> package/module is loaded. When
277AnyEvent is loaded and asked to find a suitable event model, it will 503AnyEvent is loaded and asked to find a suitable event model, it will
278first check for the presence of urxvt. 504first check for the presence of urxvt.
279 505
280The class should prove implementations for all watcher types (see 506The class should provide implementations for all watcher types (see
281L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib> 507L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib>
282(Source code) and so on for actual examples, use C<perldoc -m 508(Source code) and so on for actual examples, use C<perldoc -m
283AnyEvent::Impl::Glib> to see the sources). 509AnyEvent::Impl::Glib> to see the sources).
284 510
285The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt) 511The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
289I<rxvt-unicode> distribution. 515I<rxvt-unicode> distribution.
290 516
291I<rxvt-unicode> also cheats a bit by not providing blocking access to 517I<rxvt-unicode> also cheats a bit by not providing blocking access to
292condition variables: code blocking while waiting for a condition will 518condition variables: code blocking while waiting for a condition will
293C<die>. This still works with most modules/usages, and blocking calls must 519C<die>. This still works with most modules/usages, and blocking calls must
294not be in an interactive appliation, so it makes sense. 520not be in an interactive application, so it makes sense.
295 521
296=head1 ENVIRONMENT VARIABLES 522=head1 ENVIRONMENT VARIABLES
297 523
298The following environment variables are used by this module: 524The following environment variables are used by this module:
299 525

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines