1 | =head1 NAME |
1 | =head1 => NAME |
2 | |
2 | |
3 | AnyEvent - provide framework for multiple event loops |
3 | AnyEvent - provide framework for multiple event loops |
4 | |
4 | |
5 | EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops |
5 | EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops |
6 | |
6 | |
… | |
… | |
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 whether a condition was flagged |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
|
|
20 | $w->send; # wake up current and all future recv's |
20 | $w->wait; # enters "main loop" till $condvar gets ->send |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
21 | $w->send; # wake up current and all future wait's |
|
|
22 | |
22 | |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
24 | |
24 | |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
26 | nowadays. So what is different about AnyEvent? |
26 | nowadays. So what is different about AnyEvent? |
… | |
… | |
279 | |
279 | |
280 | Example: fork a process and wait for it |
280 | Example: fork a process and wait for it |
281 | |
281 | |
282 | my $done = AnyEvent->condvar; |
282 | my $done = AnyEvent->condvar; |
283 | |
283 | |
284 | AnyEvent::detect; # force event module to be initialised |
|
|
285 | |
|
|
286 | my $pid = fork or exit 5; |
284 | my $pid = fork or exit 5; |
287 | |
285 | |
288 | my $w = AnyEvent->child ( |
286 | my $w = AnyEvent->child ( |
289 | pid => $pid, |
287 | pid => $pid, |
290 | cb => sub { |
288 | cb => sub { |
… | |
… | |
293 | $done->send; |
291 | $done->send; |
294 | }, |
292 | }, |
295 | ); |
293 | ); |
296 | |
294 | |
297 | # do something else, then wait for process exit |
295 | # do something else, then wait for process exit |
298 | $done->wait; |
296 | $done->recv; |
299 | |
297 | |
300 | =head2 CONDITION VARIABLES |
298 | =head2 CONDITION VARIABLES |
301 | |
299 | |
302 | If you are familiar with some event loops you will know that all of them |
300 | If you are familiar with some event loops you will know that all of them |
303 | require you to run some blocking "loop", "run" or similar function that |
301 | require you to run some blocking "loop", "run" or similar function that |
… | |
… | |
326 | |
324 | |
327 | Condition variables are very useful to signal that something has finished, |
325 | Condition variables are very useful to signal that something has finished, |
328 | for example, if you write a module that does asynchronous http requests, |
326 | for example, if you write a module that does asynchronous http requests, |
329 | then a condition variable would be the ideal candidate to signal the |
327 | then a condition variable would be the ideal candidate to signal the |
330 | availability of results. The user can either act when the callback is |
328 | availability of results. The user can either act when the callback is |
331 | called or can synchronously C<< ->wait >> for the results. |
329 | called or can synchronously C<< ->recv >> for the results. |
332 | |
330 | |
333 | You can also use them to simulate traditional event loops - for example, |
331 | You can also use them to simulate traditional event loops - for example, |
334 | you can block your main program until an event occurs - for example, you |
332 | you can block your main program until an event occurs - for example, you |
335 | could C<< ->wait >> in your main program until the user clicks the Quit |
333 | could C<< ->recv >> in your main program until the user clicks the Quit |
336 | button of your app, which would C<< ->send >> the "quit" event. |
334 | button of your app, which would C<< ->send >> the "quit" event. |
337 | |
335 | |
338 | Note that condition variables recurse into the event loop - if you have |
336 | Note that condition variables recurse into the event loop - if you have |
339 | two pieces of code that call C<< ->wait >> in a round-robbin fashion, you |
337 | two pieces of code that call C<< ->recv >> in a round-robbin fashion, you |
340 | lose. Therefore, condition variables are good to export to your caller, but |
338 | lose. Therefore, condition variables are good to export to your caller, but |
341 | you should avoid making a blocking wait yourself, at least in callbacks, |
339 | you should avoid making a blocking wait yourself, at least in callbacks, |
342 | as this asks for trouble. |
340 | as this asks for trouble. |
343 | |
341 | |
344 | Condition variables are represented by hash refs in perl, and the keys |
342 | Condition variables are represented by hash refs in perl, and the keys |
… | |
… | |
365 | cb => sub { $result_ready->send }, |
363 | cb => sub { $result_ready->send }, |
366 | ); |
364 | ); |
367 | |
365 | |
368 | # this "blocks" (while handling events) till the callback |
366 | # this "blocks" (while handling events) till the callback |
369 | # calls send |
367 | # calls send |
370 | $result_ready->wait; |
368 | $result_ready->recv; |
371 | |
369 | |
372 | =head3 METHODS FOR PRODUCERS |
370 | =head3 METHODS FOR PRODUCERS |
373 | |
371 | |
374 | These methods should only be used by the producing side, i.e. the |
372 | These methods should only be used by the producing side, i.e. the |
375 | code/module that eventually sends the signal. Note that it is also |
373 | code/module that eventually sends the signal. Note that it is also |
… | |
… | |
378 | |
376 | |
379 | =over 4 |
377 | =over 4 |
380 | |
378 | |
381 | =item $cv->send (...) |
379 | =item $cv->send (...) |
382 | |
380 | |
383 | Flag the condition as ready - a running C<< ->wait >> and all further |
381 | Flag the condition as ready - a running C<< ->recv >> and all further |
384 | calls to C<wait> will (eventually) return after this method has been |
382 | calls to C<recv> will (eventually) return after this method has been |
385 | called. If nobody is waiting the send will be remembered. |
383 | called. If nobody is waiting the send will be remembered. |
386 | |
384 | |
387 | If a callback has been set on the condition variable, it is called |
385 | If a callback has been set on the condition variable, it is called |
388 | immediately from within send. |
386 | immediately from within send. |
389 | |
387 | |
390 | Any arguments passed to the C<send> call will be returned by all |
388 | Any arguments passed to the C<send> call will be returned by all |
391 | future C<< ->wait >> calls. |
389 | future C<< ->recv >> calls. |
392 | |
390 | |
393 | =item $cv->croak ($error) |
391 | =item $cv->croak ($error) |
394 | |
392 | |
395 | Similar to send, but causes all call's wait C<< ->wait >> to invoke |
393 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
396 | C<Carp::croak> with the given error message/object/scalar. |
394 | C<Carp::croak> with the given error message/object/scalar. |
397 | |
395 | |
398 | This can be used to signal any errors to the condition variable |
396 | This can be used to signal any errors to the condition variable |
399 | user/consumer. |
397 | user/consumer. |
400 | |
398 | |
401 | =item $cv->begin ([group callback]) |
399 | =item $cv->begin ([group callback]) |
402 | |
400 | |
403 | =item $cv->end |
401 | =item $cv->end |
|
|
402 | |
|
|
403 | These two methods are EXPERIMENTAL and MIGHT CHANGE. |
404 | |
404 | |
405 | These two methods can be used to combine many transactions/events into |
405 | These two methods can be used to combine many transactions/events into |
406 | one. For example, a function that pings many hosts in parallel might want |
406 | one. For example, a function that pings many hosts in parallel might want |
407 | to use a condition variable for the whole process. |
407 | to use a condition variable for the whole process. |
408 | |
408 | |
… | |
… | |
454 | These methods should only be used by the consuming side, i.e. the |
454 | These methods should only be used by the consuming side, i.e. the |
455 | code awaits the condition. |
455 | code awaits the condition. |
456 | |
456 | |
457 | =over 4 |
457 | =over 4 |
458 | |
458 | |
459 | =item $cv->wait |
459 | =item $cv->recv |
460 | |
460 | |
461 | Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak |
461 | Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak |
462 | >> methods have been called on c<$cv>, while servicing other watchers |
462 | >> methods have been called on c<$cv>, while servicing other watchers |
463 | normally. |
463 | normally. |
464 | |
464 | |
… | |
… | |
477 | caller decide whether the call will block or not (for example, by coupling |
477 | caller decide whether the call will block or not (for example, by coupling |
478 | condition variables with some kind of request results and supporting |
478 | condition variables with some kind of request results and supporting |
479 | callbacks so the caller knows that getting the result will not block, |
479 | callbacks so the caller knows that getting the result will not block, |
480 | while still suppporting blocking waits if the caller so desires). |
480 | while still suppporting blocking waits if the caller so desires). |
481 | |
481 | |
482 | Another reason I<never> to C<< ->wait >> in a module is that you cannot |
482 | Another reason I<never> to C<< ->recv >> in a module is that you cannot |
483 | sensibly have two C<< ->wait >>'s in parallel, as that would require |
483 | sensibly have two C<< ->recv >>'s in parallel, as that would require |
484 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
484 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
485 | can supply. |
485 | can supply. |
486 | |
486 | |
487 | The L<Coro> module, however, I<can> and I<does> supply coroutines and, in |
487 | The L<Coro> module, however, I<can> and I<does> supply coroutines and, in |
488 | fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe |
488 | fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe |
489 | versions and also integrates coroutines into AnyEvent, making blocking |
489 | versions and also integrates coroutines into AnyEvent, making blocking |
490 | C<< ->wait >> calls perfectly safe as long as they are done from another |
490 | C<< ->recv >> calls perfectly safe as long as they are done from another |
491 | coroutine (one that doesn't run the event loop). |
491 | coroutine (one that doesn't run the event loop). |
492 | |
492 | |
493 | You can ensure that C<< -wait >> never blocks by setting a callback and |
493 | You can ensure that C<< -recv >> never blocks by setting a callback and |
494 | only calling C<< ->wait >> from within that callback (or at a later |
494 | only calling C<< ->recv >> from within that callback (or at a later |
495 | time). This will work even when the event loop does not support blocking |
495 | time). This will work even when the event loop does not support blocking |
496 | waits otherwise. |
496 | waits otherwise. |
497 | |
497 | |
498 | =item $bool = $cv->ready |
498 | =item $bool = $cv->ready |
499 | |
499 | |
… | |
… | |
504 | |
504 | |
505 | This is a mutator function that returns the callback set and optionally |
505 | This is a mutator function that returns the callback set and optionally |
506 | replaces it before doing so. |
506 | replaces it before doing so. |
507 | |
507 | |
508 | The callback will be called when the condition becomes "true", i.e. when |
508 | The callback will be called when the condition becomes "true", i.e. when |
509 | C<send> or C<croak> are called. Calling C<wait> inside the callback |
509 | C<send> or C<croak> are called. Calling C<recv> inside the callback |
510 | or at any later time is guaranteed not to block. |
510 | or at any later time is guaranteed not to block. |
511 | |
511 | |
512 | =back |
512 | =back |
513 | |
513 | |
514 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
514 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
… | |
… | |
549 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
549 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
550 | if necessary. You should only call this function right before you would |
550 | if necessary. You should only call this function right before you would |
551 | have created an AnyEvent watcher anyway, that is, as late as possible at |
551 | have created an AnyEvent watcher anyway, that is, as late as possible at |
552 | runtime. |
552 | runtime. |
553 | |
553 | |
554 | =item AnyEvent::on_detect { BLOCK } |
554 | =item $guard = AnyEvent::post_detect { BLOCK } |
555 | |
555 | |
556 | Arranges for the code block to be executed as soon as the event model is |
556 | Arranges for the code block to be executed as soon as the event model is |
557 | autodetected (or immediately if this has already happened). |
557 | autodetected (or immediately if this has already happened). |
558 | |
558 | |
|
|
559 | If called in scalar or list context, then it creates and returns an object |
|
|
560 | that automatically removes the callback again when it is destroyed. See |
|
|
561 | L<Coro::BDB> for a case where this is useful. |
|
|
562 | |
559 | =item @AnyEvent::on_detect |
563 | =item @AnyEvent::post_detect |
560 | |
564 | |
561 | If there are any code references in this array (you can C<push> to it |
565 | If there are any code references in this array (you can C<push> to it |
562 | before or after loading AnyEvent), then they will called directly after |
566 | before or after loading AnyEvent), then they will called directly after |
563 | the event loop has been chosen. |
567 | the event loop has been chosen. |
564 | |
568 | |
565 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
569 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
566 | if it contains a true value then the event loop has already been detected, |
570 | if it contains a true value then the event loop has already been detected, |
567 | and the array will be ignored. |
571 | and the array will be ignored. |
568 | |
572 | |
569 | Best use C<AnyEvent::on_detect { BLOCK }> instead. |
573 | Best use C<AnyEvent::post_detect { BLOCK }> instead. |
570 | |
574 | |
571 | =back |
575 | =back |
572 | |
576 | |
573 | =head1 WHAT TO DO IN A MODULE |
577 | =head1 WHAT TO DO IN A MODULE |
574 | |
578 | |
… | |
… | |
578 | Be careful when you create watchers in the module body - AnyEvent will |
582 | Be careful when you create watchers in the module body - AnyEvent will |
579 | decide which event module to use as soon as the first method is called, so |
583 | decide which event module to use as soon as the first method is called, so |
580 | by calling AnyEvent in your module body you force the user of your module |
584 | by calling AnyEvent in your module body you force the user of your module |
581 | to load the event module first. |
585 | to load the event module first. |
582 | |
586 | |
583 | Never call C<< ->wait >> on a condition variable unless you I<know> that |
587 | Never call C<< ->recv >> on a condition variable unless you I<know> that |
584 | the C<< ->send >> method has been called on it already. This is |
588 | the C<< ->send >> method has been called on it already. This is |
585 | because it will stall the whole program, and the whole point of using |
589 | because it will stall the whole program, and the whole point of using |
586 | events is to stay interactive. |
590 | events is to stay interactive. |
587 | |
591 | |
588 | It is fine, however, to call C<< ->wait >> when the user of your module |
592 | It is fine, however, to call C<< ->recv >> when the user of your module |
589 | requests it (i.e. if you create a http request object ad have a method |
593 | requests it (i.e. if you create a http request object ad have a method |
590 | called C<results> that returns the results, it should call C<< ->wait >> |
594 | called C<results> that returns the results, it should call C<< ->recv >> |
591 | freely, as the user of your module knows what she is doing. always). |
595 | freely, as the user of your module knows what she is doing. always). |
592 | |
596 | |
593 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
597 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
594 | |
598 | |
595 | There will always be a single main program - the only place that should |
599 | There will always be a single main program - the only place that should |
… | |
… | |
629 | |
633 | |
630 | Provide read and write buffers and manages watchers for reads and writes. |
634 | Provide read and write buffers and manages watchers for reads and writes. |
631 | |
635 | |
632 | =item L<AnyEvent::Socket> |
636 | =item L<AnyEvent::Socket> |
633 | |
637 | |
634 | Provides a means to do non-blocking connects, accepts etc. |
638 | Provides various utility functions for (internet protocol) sockets, |
|
|
639 | addresses and name resolution. Also functions to create non-blocking tcp |
|
|
640 | connections or tcp servers, with IPv6 and SRV record support and more. |
635 | |
641 | |
636 | =item L<AnyEvent::HTTPD> |
642 | =item L<AnyEvent::HTTPD> |
637 | |
643 | |
638 | Provides a simple web application server framework. |
644 | Provides a simple web application server framework. |
639 | |
645 | |
640 | =item L<AnyEvent::DNS> |
646 | =item L<AnyEvent::DNS> |
641 | |
647 | |
642 | Provides asynchronous DNS resolver capabilities, beyond what |
648 | Provides rich asynchronous DNS resolver capabilities. |
643 | L<AnyEvent::Util> offers. |
|
|
644 | |
649 | |
645 | =item L<AnyEvent::FastPing> |
650 | =item L<AnyEvent::FastPing> |
646 | |
651 | |
647 | The fastest ping in the west. |
652 | The fastest ping in the west. |
648 | |
653 | |
… | |
… | |
665 | |
670 | |
666 | =item L<Coro> |
671 | =item L<Coro> |
667 | |
672 | |
668 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
673 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
669 | |
674 | |
|
|
675 | =item L<AnyEvent::AIO>, L<IO::AIO> |
|
|
676 | |
|
|
677 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
678 | programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent |
|
|
679 | together. |
|
|
680 | |
|
|
681 | =item L<AnyEvent::BDB>, L<BDB> |
|
|
682 | |
|
|
683 | Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses |
|
|
684 | IO::AIO and AnyEvent together. |
|
|
685 | |
670 | =item L<IO::Lambda> |
686 | =item L<IO::Lambda> |
671 | |
687 | |
672 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
688 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
673 | |
|
|
674 | =item L<IO::AIO> |
|
|
675 | |
|
|
676 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
677 | programmer. Can be trivially made to use AnyEvent. |
|
|
678 | |
|
|
679 | =item L<BDB> |
|
|
680 | |
|
|
681 | Truly asynchronous Berkeley DB access. Can be trivially made to use |
|
|
682 | AnyEvent. |
|
|
683 | |
689 | |
684 | =back |
690 | =back |
685 | |
691 | |
686 | =cut |
692 | =cut |
687 | |
693 | |
… | |
… | |
690 | no warnings; |
696 | no warnings; |
691 | use strict; |
697 | use strict; |
692 | |
698 | |
693 | use Carp; |
699 | use Carp; |
694 | |
700 | |
695 | our $VERSION = '3.4'; |
701 | our $VERSION = '3.6'; |
696 | our $MODEL; |
702 | our $MODEL; |
697 | |
703 | |
698 | our $AUTOLOAD; |
704 | our $AUTOLOAD; |
699 | our @ISA; |
705 | our @ISA; |
700 | |
706 | |
701 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
707 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
702 | |
708 | |
703 | our @REGISTRY; |
709 | our @REGISTRY; |
|
|
710 | |
|
|
711 | our %PROTOCOL; # (ipv4|ipv6) => (1|2) |
|
|
712 | |
|
|
713 | { |
|
|
714 | my $idx; |
|
|
715 | $PROTOCOL{$_} = ++$idx |
|
|
716 | for split /\s*,\s*/, $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
|
|
717 | } |
704 | |
718 | |
705 | my @models = ( |
719 | my @models = ( |
706 | [EV:: => AnyEvent::Impl::EV::], |
720 | [EV:: => AnyEvent::Impl::EV::], |
707 | [Event:: => AnyEvent::Impl::Event::], |
721 | [Event:: => AnyEvent::Impl::Event::], |
708 | [Tk:: => AnyEvent::Impl::Tk::], |
722 | [Tk:: => AnyEvent::Impl::Tk::], |
… | |
… | |
716 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
730 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
717 | ); |
731 | ); |
718 | |
732 | |
719 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
733 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
720 | |
734 | |
721 | our @on_detect; |
735 | our @post_detect; |
722 | |
736 | |
723 | sub on_detect(&) { |
737 | sub post_detect(&) { |
|
|
738 | my ($cb) = @_; |
|
|
739 | |
724 | if ($MODEL) { |
740 | if ($MODEL) { |
725 | $_[0]->(); |
741 | $cb->(); |
|
|
742 | |
|
|
743 | 1 |
726 | } else { |
744 | } else { |
727 | push @on_detect, $_[0]; |
745 | push @post_detect, $cb; |
|
|
746 | |
|
|
747 | defined wantarray |
|
|
748 | ? bless \$cb, "AnyEvent::Util::PostDetect" |
|
|
749 | : () |
728 | } |
750 | } |
|
|
751 | } |
|
|
752 | |
|
|
753 | sub AnyEvent::Util::PostDetect::DESTROY { |
|
|
754 | @post_detect = grep $_ != ${$_[0]}, @post_detect; |
729 | } |
755 | } |
730 | |
756 | |
731 | sub detect() { |
757 | sub detect() { |
732 | unless ($MODEL) { |
758 | unless ($MODEL) { |
733 | no strict 'refs'; |
759 | no strict 'refs'; |
… | |
… | |
775 | } |
801 | } |
776 | |
802 | |
777 | unshift @ISA, $MODEL; |
803 | unshift @ISA, $MODEL; |
778 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
804 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
779 | |
805 | |
780 | (shift @on_detect)->() while @on_detect; |
806 | (shift @post_detect)->() while @post_detect; |
781 | } |
807 | } |
782 | |
808 | |
783 | $MODEL |
809 | $MODEL |
784 | } |
810 | } |
785 | |
811 | |
… | |
… | |
795 | $class->$func (@_); |
821 | $class->$func (@_); |
796 | } |
822 | } |
797 | |
823 | |
798 | package AnyEvent::Base; |
824 | package AnyEvent::Base; |
799 | |
825 | |
800 | # default implementation for ->condvar, ->wait, ->broadcast |
826 | # default implementation for ->condvar |
801 | |
827 | |
802 | sub condvar { |
828 | sub condvar { |
803 | bless \my $flag, "AnyEvent::Base::CondVar" |
829 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
804 | } |
|
|
805 | |
|
|
806 | sub AnyEvent::Base::CondVar::broadcast { |
|
|
807 | ${$_[0]}++; |
|
|
808 | } |
|
|
809 | |
|
|
810 | sub AnyEvent::Base::CondVar::wait { |
|
|
811 | AnyEvent->one_event while !${$_[0]}; |
|
|
812 | } |
830 | } |
813 | |
831 | |
814 | # default implementation for ->signal |
832 | # default implementation for ->signal |
815 | |
833 | |
816 | our %SIG_CB; |
834 | our %SIG_CB; |
… | |
… | |
890 | delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; |
908 | delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; |
891 | |
909 | |
892 | undef $CHLD_W unless keys %PID_CB; |
910 | undef $CHLD_W unless keys %PID_CB; |
893 | } |
911 | } |
894 | |
912 | |
|
|
913 | package AnyEvent::CondVar; |
|
|
914 | |
|
|
915 | our @ISA = AnyEvent::CondVar::Base::; |
|
|
916 | |
|
|
917 | package AnyEvent::CondVar::Base; |
|
|
918 | |
|
|
919 | sub _send { |
|
|
920 | # nop |
|
|
921 | } |
|
|
922 | |
|
|
923 | sub send { |
|
|
924 | my $cv = shift; |
|
|
925 | $cv->{_ae_sent} = [@_]; |
|
|
926 | (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb}; |
|
|
927 | $cv->_send; |
|
|
928 | } |
|
|
929 | |
|
|
930 | sub croak { |
|
|
931 | $_[0]{_ae_croak} = $_[1]; |
|
|
932 | $_[0]->send; |
|
|
933 | } |
|
|
934 | |
|
|
935 | sub ready { |
|
|
936 | $_[0]{_ae_sent} |
|
|
937 | } |
|
|
938 | |
|
|
939 | sub _wait { |
|
|
940 | AnyEvent->one_event while !$_[0]{_ae_sent}; |
|
|
941 | } |
|
|
942 | |
|
|
943 | sub recv { |
|
|
944 | $_[0]->_wait; |
|
|
945 | |
|
|
946 | Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; |
|
|
947 | wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] |
|
|
948 | } |
|
|
949 | |
|
|
950 | sub cb { |
|
|
951 | $_[0]{_ae_cb} = $_[1] if @_ > 1; |
|
|
952 | $_[0]{_ae_cb} |
|
|
953 | } |
|
|
954 | |
|
|
955 | sub begin { |
|
|
956 | ++$_[0]{_ae_counter}; |
|
|
957 | $_[0]{_ae_end_cb} = $_[1] if @_ > 1; |
|
|
958 | } |
|
|
959 | |
|
|
960 | sub end { |
|
|
961 | return if --$_[0]{_ae_counter}; |
|
|
962 | &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } }; |
|
|
963 | } |
|
|
964 | |
|
|
965 | # undocumented/compatibility with pre-3.4 |
|
|
966 | *broadcast = \&send; |
|
|
967 | *wait = \&_wait; |
|
|
968 | |
895 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
969 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
896 | |
970 | |
897 | This is an advanced topic that you do not normally need to use AnyEvent in |
971 | This is an advanced topic that you do not normally need to use AnyEvent in |
898 | a module. This section is only of use to event loop authors who want to |
972 | a module. This section is only of use to event loop authors who want to |
899 | provide AnyEvent compatibility. |
973 | provide AnyEvent compatibility. |
… | |
… | |
967 | |
1041 | |
968 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
1042 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
969 | could start your program like this: |
1043 | could start your program like this: |
970 | |
1044 | |
971 | PERL_ANYEVENT_MODEL=Perl perl ... |
1045 | PERL_ANYEVENT_MODEL=Perl perl ... |
|
|
1046 | |
|
|
1047 | =item C<PERL_ANYEVENT_PROTOCOLS> |
|
|
1048 | |
|
|
1049 | Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences |
|
|
1050 | for IPv4 or IPv6. The default is unspecified (and might change, or be the result |
|
|
1051 | of autoprobing). |
|
|
1052 | |
|
|
1053 | Must be set to a comma-separated list of protocols or address families, |
|
|
1054 | current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be |
|
|
1055 | used, and preference will be given to protocols mentioned earlier in the |
|
|
1056 | list. |
|
|
1057 | |
|
|
1058 | This variable can effectively be used for denial-of-service attacks |
|
|
1059 | against local programs (e.g. when setuid), although the impact is likely |
|
|
1060 | small, as the program has to handle connection errors already- |
|
|
1061 | |
|
|
1062 | Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6, |
|
|
1063 | but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4> |
|
|
1064 | - only support IPv4, never try to resolve or contact IPv6 |
|
|
1065 | addressses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or |
|
|
1066 | IPv6, but prefer IPv6 over IPv4. |
|
|
1067 | |
|
|
1068 | =item C<PERL_ANYEVENT_EDNS0> |
|
|
1069 | |
|
|
1070 | Used by L<AnyEvent::DNS> to decide wether to use the EDNS0 extension |
|
|
1071 | for DNS. This extension is generally useful to reduce DNS traffic, but |
|
|
1072 | some (broken) firewalls drop such DNS packets, which is why it is off by |
|
|
1073 | default. |
|
|
1074 | |
|
|
1075 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
|
|
1076 | EDNS0 in its DNS requests. |
972 | |
1077 | |
973 | =back |
1078 | =back |
974 | |
1079 | |
975 | =head1 EXAMPLE PROGRAM |
1080 | =head1 EXAMPLE PROGRAM |
976 | |
1081 | |
… | |
… | |
987 | poll => 'r', |
1092 | poll => 'r', |
988 | cb => sub { |
1093 | cb => sub { |
989 | warn "io event <$_[0]>\n"; # will always output <r> |
1094 | warn "io event <$_[0]>\n"; # will always output <r> |
990 | chomp (my $input = <STDIN>); # read a line |
1095 | chomp (my $input = <STDIN>); # read a line |
991 | warn "read: $input\n"; # output what has been read |
1096 | warn "read: $input\n"; # output what has been read |
992 | $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i |
1097 | $cv->send if $input =~ /^q/i; # quit program if /^q/i |
993 | }, |
1098 | }, |
994 | ); |
1099 | ); |
995 | |
1100 | |
996 | my $time_watcher; # can only be used once |
1101 | my $time_watcher; # can only be used once |
997 | |
1102 | |
… | |
… | |
1002 | }); |
1107 | }); |
1003 | } |
1108 | } |
1004 | |
1109 | |
1005 | new_timer; # create first timer |
1110 | new_timer; # create first timer |
1006 | |
1111 | |
1007 | $cv->wait; # wait until user enters /^q/i |
1112 | $cv->recv; # wait until user enters /^q/i |
1008 | |
1113 | |
1009 | =head1 REAL-WORLD EXAMPLE |
1114 | =head1 REAL-WORLD EXAMPLE |
1010 | |
1115 | |
1011 | Consider the L<Net::FCP> module. It features (among others) the following |
1116 | Consider the L<Net::FCP> module. It features (among others) the following |
1012 | API calls, which are to freenet what HTTP GET requests are to http: |
1117 | API calls, which are to freenet what HTTP GET requests are to http: |
… | |
… | |
1068 | |
1173 | |
1069 | sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf}; |
1174 | sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf}; |
1070 | |
1175 | |
1071 | if (end-of-file or data complete) { |
1176 | if (end-of-file or data complete) { |
1072 | $txn->{result} = $txn->{buf}; |
1177 | $txn->{result} = $txn->{buf}; |
1073 | $txn->{finished}->broadcast; |
1178 | $txn->{finished}->send; |
1074 | $txb->{cb}->($txn) of $txn->{cb}; # also call callback |
1179 | $txb->{cb}->($txn) of $txn->{cb}; # also call callback |
1075 | } |
1180 | } |
1076 | |
1181 | |
1077 | The C<result> method, finally, just waits for the finished signal (if the |
1182 | The C<result> method, finally, just waits for the finished signal (if the |
1078 | request was already finished, it doesn't wait, of course, and returns the |
1183 | request was already finished, it doesn't wait, of course, and returns the |
1079 | data: |
1184 | data: |
1080 | |
1185 | |
1081 | $txn->{finished}->wait; |
1186 | $txn->{finished}->recv; |
1082 | return $txn->{result}; |
1187 | return $txn->{result}; |
1083 | |
1188 | |
1084 | The actual code goes further and collects all errors (C<die>s, exceptions) |
1189 | The actual code goes further and collects all errors (C<die>s, exceptions) |
1085 | that occured during request processing. The C<result> method detects |
1190 | that occured during request processing. The C<result> method detects |
1086 | whether an exception as thrown (it is stored inside the $txn object) |
1191 | whether an exception as thrown (it is stored inside the $txn object) |
… | |
… | |
1121 | |
1226 | |
1122 | my $quit = AnyEvent->condvar; |
1227 | my $quit = AnyEvent->condvar; |
1123 | |
1228 | |
1124 | $fcp->txn_client_get ($url)->cb (sub { |
1229 | $fcp->txn_client_get ($url)->cb (sub { |
1125 | ... |
1230 | ... |
1126 | $quit->broadcast; |
1231 | $quit->send; |
1127 | }); |
1232 | }); |
1128 | |
1233 | |
1129 | $quit->wait; |
1234 | $quit->recv; |
1130 | |
1235 | |
1131 | |
1236 | |
1132 | =head1 BENCHMARKS |
1237 | =head1 BENCHMARKS |
1133 | |
1238 | |
1134 | To give you an idea of the performance and overheads that AnyEvent adds |
1239 | To give you an idea of the performance and overheads that AnyEvent adds |
… | |
… | |
1163 | all watchers, to avoid adding memory overhead. That means closure creation |
1268 | all watchers, to avoid adding memory overhead. That means closure creation |
1164 | and memory usage is not included in the figures. |
1269 | and memory usage is not included in the figures. |
1165 | |
1270 | |
1166 | I<invoke> is the time, in microseconds, used to invoke a simple |
1271 | I<invoke> is the time, in microseconds, used to invoke a simple |
1167 | callback. The callback simply counts down a Perl variable and after it was |
1272 | callback. The callback simply counts down a Perl variable and after it was |
1168 | invoked "watcher" times, it would C<< ->broadcast >> a condvar once to |
1273 | invoked "watcher" times, it would C<< ->send >> a condvar once to |
1169 | signal the end of this phase. |
1274 | signal the end of this phase. |
1170 | |
1275 | |
1171 | I<destroy> is the time, in microseconds, that it takes to destroy a single |
1276 | I<destroy> is the time, in microseconds, that it takes to destroy a single |
1172 | watcher. |
1277 | watcher. |
1173 | |
1278 | |
… | |
… | |
1426 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
1531 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
1427 | |
1532 | |
1428 | |
1533 | |
1429 | =head1 SEE ALSO |
1534 | =head1 SEE ALSO |
1430 | |
1535 | |
|
|
1536 | Utility functions: L<AnyEvent::Util>. |
|
|
1537 | |
1431 | Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, |
1538 | Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, |
1432 | L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. |
1539 | L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. |
1433 | |
1540 | |
1434 | Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, |
1541 | Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, |
1435 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, |
1542 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, |
1436 | L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, |
1543 | L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, |
1437 | L<AnyEvent::Impl::POE>. |
1544 | L<AnyEvent::Impl::POE>. |
1438 | |
1545 | |
|
|
1546 | Non-blocking file handles, sockets, TCP clients and |
|
|
1547 | servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>. |
|
|
1548 | |
|
|
1549 | Asynchronous DNS: L<AnyEvent::DNS>. |
|
|
1550 | |
1439 | Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, |
1551 | Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>, |
1440 | |
1552 | |
1441 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. |
1553 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
1442 | |
1554 | |
1443 | |
1555 | |
1444 | =head1 AUTHOR |
1556 | =head1 AUTHOR |
1445 | |
1557 | |
1446 | Marc Lehmann <schmorp@schmorp.de> |
1558 | Marc Lehmann <schmorp@schmorp.de> |