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.107 by root, Tue May 6 12:15:50 2008 UTC vs.
Revision 1.126 by root, Fri May 23 23:44:55 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
5EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops 5EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops
6 6
7=head1 SYNOPSIS 7=head1 SYNOPSIS
8 8
9 use AnyEvent; 9 use AnyEvent;
10 10
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
25Glib, POE, IO::Async, Event... CPAN offers event models by the dozen 25Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26nowadays. So what is different about AnyEvent? 26nowadays. So what is different about AnyEvent?
78The interface itself is vaguely similar, but not identical to the L<Event> 78The interface itself is vaguely similar, but not identical to the L<Event>
79module. 79module.
80 80
81During the first call of any watcher-creation method, the module tries 81During the first call of any watcher-creation method, the module tries
82to detect the currently loaded event loop by probing whether one of the 82to detect the currently loaded event loop by probing whether one of the
83following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>, 83following modules is already loaded: L<EV>,
84L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>, 84L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
85L<POE>. The first one found is used. If none are found, the module tries 85L<POE>. The first one found is used. If none are found, the module tries
86to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl 86to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
87adaptor should always succeed) in the order given. The first one that can 87adaptor should always succeed) in the order given. The first one that can
88be successfully loaded will be used. If, after this, still none could be 88be successfully loaded will be used. If, after this, still none could be
278C<fork> the child (alternatively, you can call C<AnyEvent::detect>). 278C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
279 279
280Example: fork a process and wait for it 280Example: fork a process and wait for it
281 281
282 my $done = AnyEvent->condvar; 282 my $done = AnyEvent->condvar;
283
284 AnyEvent::detect; # force event module to be initialised
285 283
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,
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
302If you are familiar with some event loops you will know that all of them 300If you are familiar with some event loops you will know that all of them
303require you to run some blocking "loop", "run" or similar function that 301require you to run some blocking "loop", "run" or similar function that
326 324
327Condition variables are very useful to signal that something has finished, 325Condition variables are very useful to signal that something has finished,
328for example, if you write a module that does asynchronous http requests, 326for example, if you write a module that does asynchronous http requests,
329then a condition variable would be the ideal candidate to signal the 327then a condition variable would be the ideal candidate to signal the
330availability of results. The user can either act when the callback is 328availability of results. The user can either act when the callback is
331called or can synchronously C<< ->wait >> for the results. 329called or can synchronously C<< ->recv >> for the results.
332 330
333You can also use them to simulate traditional event loops - for example, 331You can also use them to simulate traditional event loops - for example,
334you can block your main program until an event occurs - for example, you 332you can block your main program until an event occurs - for example, you
335could C<< ->wait >> in your main program until the user clicks the Quit 333could C<< ->recv >> in your main program until the user clicks the Quit
336button of your app, which would C<< ->send >> the "quit" event. 334button of your app, which would C<< ->send >> the "quit" event.
337 335
338Note that condition variables recurse into the event loop - if you have 336Note that condition variables recurse into the event loop - if you have
339two pieces of code that call C<< ->wait >> in a round-robbin fashion, you 337two pieces of code that call C<< ->recv >> in a round-robbin fashion, you
340lose. Therefore, condition variables are good to export to your caller, but 338lose. Therefore, condition variables are good to export to your caller, but
341you should avoid making a blocking wait yourself, at least in callbacks, 339you should avoid making a blocking wait yourself, at least in callbacks,
342as this asks for trouble. 340as this asks for trouble.
343 341
344Condition variables are represented by hash refs in perl, and the keys 342Condition 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
374These methods should only be used by the producing side, i.e. the 372These methods should only be used by the producing side, i.e. the
375code/module that eventually sends the signal. Note that it is also 373code/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
383Flag the condition as ready - a running C<< ->wait >> and all further 381Flag the condition as ready - a running C<< ->recv >> and all further
384calls to C<wait> will (eventually) return after this method has been 382calls to C<recv> will (eventually) return after this method has been
385called. If nobody is waiting the send will be remembered. 383called. If nobody is waiting the send will be remembered.
386 384
387If a callback has been set on the condition variable, it is called 385If a callback has been set on the condition variable, it is called
388immediately from within send. 386immediately from within send.
389 387
390Any arguments passed to the C<send> call will be returned by all 388Any arguments passed to the C<send> call will be returned by all
391future C<< ->wait >> calls. 389future C<< ->recv >> calls.
392 390
393=item $cv->croak ($error) 391=item $cv->croak ($error)
394 392
395Similar to send, but causes all call's wait C<< ->wait >> to invoke 393Similar to send, but causes all call's to C<< ->recv >> to invoke
396C<Carp::croak> with the given error message/object/scalar. 394C<Carp::croak> with the given error message/object/scalar.
397 395
398This can be used to signal any errors to the condition variable 396This can be used to signal any errors to the condition variable
399user/consumer. 397user/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
403These two methods are EXPERIMENTAL and MIGHT CHANGE.
404 404
405These two methods can be used to combine many transactions/events into 405These two methods can be used to combine many transactions/events into
406one. For example, a function that pings many hosts in parallel might want 406one. For example, a function that pings many hosts in parallel might want
407to use a condition variable for the whole process. 407to use a condition variable for the whole process.
408 408
454These methods should only be used by the consuming side, i.e. the 454These methods should only be used by the consuming side, i.e. the
455code awaits the condition. 455code awaits the condition.
456 456
457=over 4 457=over 4
458 458
459=item $cv->wait 459=item $cv->recv
460 460
461Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak 461Wait (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
463normally. 463normally.
464 464
477caller decide whether the call will block or not (for example, by coupling 477caller decide whether the call will block or not (for example, by coupling
478condition variables with some kind of request results and supporting 478condition variables with some kind of request results and supporting
479callbacks so the caller knows that getting the result will not block, 479callbacks so the caller knows that getting the result will not block,
480while still suppporting blocking waits if the caller so desires). 480while still suppporting blocking waits if the caller so desires).
481 481
482Another reason I<never> to C<< ->wait >> in a module is that you cannot 482Another reason I<never> to C<< ->recv >> in a module is that you cannot
483sensibly have two C<< ->wait >>'s in parallel, as that would require 483sensibly have two C<< ->recv >>'s in parallel, as that would require
484multiple interpreters or coroutines/threads, none of which C<AnyEvent> 484multiple interpreters or coroutines/threads, none of which C<AnyEvent>
485can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and 485can supply.
486L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s
487from different coroutines, however).
488 486
487The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
488fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
489versions and also integrates coroutines into AnyEvent, making blocking
490C<< ->recv >> calls perfectly safe as long as they are done from another
491coroutine (one that doesn't run the event loop).
492
489You can ensure that C<< -wait >> never blocks by setting a callback and 493You can ensure that C<< -recv >> never blocks by setting a callback and
490only calling C<< ->wait >> from within that callback (or at a later 494only calling C<< ->recv >> from within that callback (or at a later
491time). This will work even when the event loop does not support blocking 495time). This will work even when the event loop does not support blocking
492waits otherwise. 496waits otherwise.
493 497
494=item $bool = $cv->ready 498=item $bool = $cv->ready
495 499
500 504
501This is a mutator function that returns the callback set and optionally 505This is a mutator function that returns the callback set and optionally
502replaces it before doing so. 506replaces it before doing so.
503 507
504The callback will be called when the condition becomes "true", i.e. when 508The callback will be called when the condition becomes "true", i.e. when
505C<send> or C<croak> are called. Calling C<wait> inside the callback 509C<send> or C<croak> are called. Calling C<recv> inside the callback
506or at any later time is guaranteed not to block. 510or at any later time is guaranteed not to block.
507 511
508=back 512=back
509 513
510=head1 GLOBAL VARIABLES AND FUNCTIONS 514=head1 GLOBAL VARIABLES AND FUNCTIONS
519C<AnyEvent::Impl:xxx> modules, but can be any other class in the case 523C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
520AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). 524AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
521 525
522The known classes so far are: 526The known classes so far are:
523 527
524 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
525 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
526 AnyEvent::Impl::EV based on EV (an interface to libev, best choice). 528 AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
527 AnyEvent::Impl::Event based on Event, second best choice. 529 AnyEvent::Impl::Event based on Event, second best choice.
528 AnyEvent::Impl::Perl pure-perl implementation, fast and portable. 530 AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
529 AnyEvent::Impl::Glib based on Glib, third-best choice. 531 AnyEvent::Impl::Glib based on Glib, third-best choice.
530 AnyEvent::Impl::Tk based on Tk, very bad choice. 532 AnyEvent::Impl::Tk based on Tk, very bad choice.
547Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 549Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
548if necessary. You should only call this function right before you would 550if necessary. You should only call this function right before you would
549have created an AnyEvent watcher anyway, that is, as late as possible at 551have created an AnyEvent watcher anyway, that is, as late as possible at
550runtime. 552runtime.
551 553
554=item $guard = AnyEvent::post_detect { BLOCK }
555
556Arranges for the code block to be executed as soon as the event model is
557autodetected (or immediately if this has already happened).
558
559If called in scalar or list context, then it creates and returns an object
560that automatically removes the callback again when it is destroyed. See
561L<Coro::BDB> for a case where this is useful.
562
563=item @AnyEvent::post_detect
564
565If there are any code references in this array (you can C<push> to it
566before or after loading AnyEvent), then they will called directly after
567the event loop has been chosen.
568
569You should check C<$AnyEvent::MODEL> before adding to this array, though:
570if it contains a true value then the event loop has already been detected,
571and the array will be ignored.
572
573Best use C<AnyEvent::post_detect { BLOCK }> instead.
574
552=back 575=back
553 576
554=head1 WHAT TO DO IN A MODULE 577=head1 WHAT TO DO IN A MODULE
555 578
556As a module author, you should C<use AnyEvent> and call AnyEvent methods 579As a module author, you should C<use AnyEvent> and call AnyEvent methods
559Be careful when you create watchers in the module body - AnyEvent will 582Be careful when you create watchers in the module body - AnyEvent will
560decide which event module to use as soon as the first method is called, so 583decide which event module to use as soon as the first method is called, so
561by calling AnyEvent in your module body you force the user of your module 584by calling AnyEvent in your module body you force the user of your module
562to load the event module first. 585to load the event module first.
563 586
564Never call C<< ->wait >> on a condition variable unless you I<know> that 587Never call C<< ->recv >> on a condition variable unless you I<know> that
565the C<< ->send >> method has been called on it already. This is 588the C<< ->send >> method has been called on it already. This is
566because it will stall the whole program, and the whole point of using 589because it will stall the whole program, and the whole point of using
567events is to stay interactive. 590events is to stay interactive.
568 591
569It is fine, however, to call C<< ->wait >> when the user of your module 592It is fine, however, to call C<< ->recv >> when the user of your module
570requests it (i.e. if you create a http request object ad have a method 593requests it (i.e. if you create a http request object ad have a method
571called C<results> that returns the results, it should call C<< ->wait >> 594called C<results> that returns the results, it should call C<< ->recv >>
572freely, as the user of your module knows what she is doing. always). 595freely, as the user of your module knows what she is doing. always).
573 596
574=head1 WHAT TO DO IN THE MAIN PROGRAM 597=head1 WHAT TO DO IN THE MAIN PROGRAM
575 598
576There will always be a single main program - the only place that should 599There will always be a single main program - the only place that should
610 633
611Provide read and write buffers and manages watchers for reads and writes. 634Provide read and write buffers and manages watchers for reads and writes.
612 635
613=item L<AnyEvent::Socket> 636=item L<AnyEvent::Socket>
614 637
615Provides a means to do non-blocking connects, accepts etc. 638Provides various utility functions for (internet protocol) sockets,
639addresses and name resolution. Also functions to create non-blocking tcp
640connections or tcp servers, with IPv6 and SRV record support and more.
616 641
617=item L<AnyEvent::HTTPD> 642=item L<AnyEvent::HTTPD>
618 643
619Provides a simple web application server framework. 644Provides a simple web application server framework.
620 645
621=item L<AnyEvent::DNS> 646=item L<AnyEvent::DNS>
622 647
623Provides asynchronous DNS resolver capabilities, beyond what 648Provides rich asynchronous DNS resolver capabilities.
624L<AnyEvent::Util> offers.
625 649
626=item L<AnyEvent::FastPing> 650=item L<AnyEvent::FastPing>
627 651
628The fastest ping in the west. 652The fastest ping in the west.
629 653
644 668
645High level API for event-based execution flow control. 669High level API for event-based execution flow control.
646 670
647=item L<Coro> 671=item L<Coro>
648 672
649Has special support for AnyEvent. 673Has special support for AnyEvent via L<Coro::AnyEvent>.
674
675=item L<AnyEvent::AIO>, L<IO::AIO>
676
677Truly asynchronous I/O, should be in the toolbox of every event
678programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
679together.
680
681=item L<AnyEvent::BDB>, L<BDB>
682
683Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
684IO::AIO and AnyEvent together.
650 685
651=item L<IO::Lambda> 686=item L<IO::Lambda>
652 687
653The lambda approach to I/O - don't ask, look there. Can use AnyEvent. 688The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
654
655=item L<IO::AIO>
656
657Truly asynchronous I/O, should be in the toolbox of every event
658programmer. Can be trivially made to use AnyEvent.
659
660=item L<BDB>
661
662Truly asynchronous Berkeley DB access. Can be trivially made to use
663AnyEvent.
664 689
665=back 690=back
666 691
667=cut 692=cut
668 693
671no warnings; 696no warnings;
672use strict; 697use strict;
673 698
674use Carp; 699use Carp;
675 700
676our $VERSION = '3.3'; 701our $VERSION = '3.6';
677our $MODEL; 702our $MODEL;
678 703
679our $AUTOLOAD; 704our $AUTOLOAD;
680our @ISA; 705our @ISA;
681 706
682our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; 707our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
683 708
684our @REGISTRY; 709our @REGISTRY;
685 710
711our %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}
718
686my @models = ( 719my @models = (
687 [Coro::EV:: => AnyEvent::Impl::CoroEV::],
688 [Coro::Event:: => AnyEvent::Impl::CoroEvent::],
689 [EV:: => AnyEvent::Impl::EV::], 720 [EV:: => AnyEvent::Impl::EV::],
690 [Event:: => AnyEvent::Impl::Event::], 721 [Event:: => AnyEvent::Impl::Event::],
691 [Tk:: => AnyEvent::Impl::Tk::], 722 [Tk:: => AnyEvent::Impl::Tk::],
692 [Wx:: => AnyEvent::Impl::POE::], 723 [Wx:: => AnyEvent::Impl::POE::],
693 [Prima:: => AnyEvent::Impl::POE::], 724 [Prima:: => AnyEvent::Impl::POE::],
699 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 730 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
700); 731);
701 732
702our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); 733our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY);
703 734
735our @post_detect;
736
737sub post_detect(&) {
738 my ($cb) = @_;
739
740 if ($MODEL) {
741 $cb->();
742
743 1
744 } else {
745 push @post_detect, $cb;
746
747 defined wantarray
748 ? bless \$cb, "AnyEvent::Util::PostDetect"
749 : ()
750 }
751}
752
753sub AnyEvent::Util::PostDetect::DESTROY {
754 @post_detect = grep $_ != ${$_[0]}, @post_detect;
755}
756
704sub detect() { 757sub detect() {
705 unless ($MODEL) { 758 unless ($MODEL) {
706 no strict 'refs'; 759 no strict 'refs';
707 760
708 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 761 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
741 last; 794 last;
742 } 795 }
743 } 796 }
744 797
745 $MODEL 798 $MODEL
746 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) or Glib."; 799 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
747 } 800 }
748 } 801 }
749 802
750 unshift @ISA, $MODEL; 803 unshift @ISA, $MODEL;
751 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 804 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
805
806 (shift @post_detect)->() while @post_detect;
752 } 807 }
753 808
754 $MODEL 809 $MODEL
755} 810}
756 811
766 $class->$func (@_); 821 $class->$func (@_);
767} 822}
768 823
769package AnyEvent::Base; 824package AnyEvent::Base;
770 825
771# default implementation for ->condvar, ->wait, ->broadcast 826# default implementation for ->condvar
772 827
773sub condvar { 828sub condvar {
774 bless \my $flag, "AnyEvent::Base::CondVar" 829 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
775}
776
777sub AnyEvent::Base::CondVar::broadcast {
778 ${$_[0]}++;
779}
780
781sub AnyEvent::Base::CondVar::wait {
782 AnyEvent->one_event while !${$_[0]};
783} 830}
784 831
785# default implementation for ->signal 832# default implementation for ->signal
786 833
787our %SIG_CB; 834our %SIG_CB;
861 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 908 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
862 909
863 undef $CHLD_W unless keys %PID_CB; 910 undef $CHLD_W unless keys %PID_CB;
864} 911}
865 912
913package AnyEvent::CondVar;
914
915our @ISA = AnyEvent::CondVar::Base::;
916
917package AnyEvent::CondVar::Base;
918
919sub _send {
920 # nop
921}
922
923sub send {
924 my $cv = shift;
925 $cv->{_ae_sent} = [@_];
926 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb};
927 $cv->_send;
928}
929
930sub croak {
931 $_[0]{_ae_croak} = $_[1];
932 $_[0]->send;
933}
934
935sub ready {
936 $_[0]{_ae_sent}
937}
938
939sub _wait {
940 AnyEvent->one_event while !$_[0]{_ae_sent};
941}
942
943sub 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
950sub cb {
951 $_[0]{_ae_cb} = $_[1] if @_ > 1;
952 $_[0]{_ae_cb}
953}
954
955sub begin {
956 ++$_[0]{_ae_counter};
957 $_[0]{_ae_end_cb} = $_[1] if @_ > 1;
958}
959
960sub 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
866=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 969=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
867 970
868This is an advanced topic that you do not normally need to use AnyEvent in 971This is an advanced topic that you do not normally need to use AnyEvent in
869a module. This section is only of use to event loop authors who want to 972a module. This section is only of use to event loop authors who want to
870provide AnyEvent compatibility. 973provide AnyEvent compatibility.
938 1041
939For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you 1042For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
940could start your program like this: 1043could start your program like this:
941 1044
942 PERL_ANYEVENT_MODEL=Perl perl ... 1045 PERL_ANYEVENT_MODEL=Perl perl ...
1046
1047=item C<PERL_ANYEVENT_PROTOCOLS>
1048
1049Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1050for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1051of autoprobing).
1052
1053Must be set to a comma-separated list of protocols or address families,
1054current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1055used, and preference will be given to protocols mentioned earlier in the
1056list.
1057
1058Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1059but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1060- only support IPv4, never try to resolve or contact IPv6
1061addressses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1062IPv6, but prefer IPv6 over IPv4.
943 1063
944=back 1064=back
945 1065
946=head1 EXAMPLE PROGRAM 1066=head1 EXAMPLE PROGRAM
947 1067
958 poll => 'r', 1078 poll => 'r',
959 cb => sub { 1079 cb => sub {
960 warn "io event <$_[0]>\n"; # will always output <r> 1080 warn "io event <$_[0]>\n"; # will always output <r>
961 chomp (my $input = <STDIN>); # read a line 1081 chomp (my $input = <STDIN>); # read a line
962 warn "read: $input\n"; # output what has been read 1082 warn "read: $input\n"; # output what has been read
963 $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i 1083 $cv->send if $input =~ /^q/i; # quit program if /^q/i
964 }, 1084 },
965 ); 1085 );
966 1086
967 my $time_watcher; # can only be used once 1087 my $time_watcher; # can only be used once
968 1088
973 }); 1093 });
974 } 1094 }
975 1095
976 new_timer; # create first timer 1096 new_timer; # create first timer
977 1097
978 $cv->wait; # wait until user enters /^q/i 1098 $cv->recv; # wait until user enters /^q/i
979 1099
980=head1 REAL-WORLD EXAMPLE 1100=head1 REAL-WORLD EXAMPLE
981 1101
982Consider the L<Net::FCP> module. It features (among others) the following 1102Consider the L<Net::FCP> module. It features (among others) the following
983API calls, which are to freenet what HTTP GET requests are to http: 1103API calls, which are to freenet what HTTP GET requests are to http:
1039 1159
1040 sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf}; 1160 sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf};
1041 1161
1042 if (end-of-file or data complete) { 1162 if (end-of-file or data complete) {
1043 $txn->{result} = $txn->{buf}; 1163 $txn->{result} = $txn->{buf};
1044 $txn->{finished}->broadcast; 1164 $txn->{finished}->send;
1045 $txb->{cb}->($txn) of $txn->{cb}; # also call callback 1165 $txb->{cb}->($txn) of $txn->{cb}; # also call callback
1046 } 1166 }
1047 1167
1048The C<result> method, finally, just waits for the finished signal (if the 1168The C<result> method, finally, just waits for the finished signal (if the
1049request was already finished, it doesn't wait, of course, and returns the 1169request was already finished, it doesn't wait, of course, and returns the
1050data: 1170data:
1051 1171
1052 $txn->{finished}->wait; 1172 $txn->{finished}->recv;
1053 return $txn->{result}; 1173 return $txn->{result};
1054 1174
1055The actual code goes further and collects all errors (C<die>s, exceptions) 1175The actual code goes further and collects all errors (C<die>s, exceptions)
1056that occured during request processing. The C<result> method detects 1176that occured during request processing. The C<result> method detects
1057whether an exception as thrown (it is stored inside the $txn object) 1177whether an exception as thrown (it is stored inside the $txn object)
1092 1212
1093 my $quit = AnyEvent->condvar; 1213 my $quit = AnyEvent->condvar;
1094 1214
1095 $fcp->txn_client_get ($url)->cb (sub { 1215 $fcp->txn_client_get ($url)->cb (sub {
1096 ... 1216 ...
1097 $quit->broadcast; 1217 $quit->send;
1098 }); 1218 });
1099 1219
1100 $quit->wait; 1220 $quit->recv;
1101 1221
1102 1222
1103=head1 BENCHMARKS 1223=head1 BENCHMARKS
1104 1224
1105To give you an idea of the performance and overheads that AnyEvent adds 1225To give you an idea of the performance and overheads that AnyEvent adds
1134all watchers, to avoid adding memory overhead. That means closure creation 1254all watchers, to avoid adding memory overhead. That means closure creation
1135and memory usage is not included in the figures. 1255and memory usage is not included in the figures.
1136 1256
1137I<invoke> is the time, in microseconds, used to invoke a simple 1257I<invoke> is the time, in microseconds, used to invoke a simple
1138callback. The callback simply counts down a Perl variable and after it was 1258callback. The callback simply counts down a Perl variable and after it was
1139invoked "watcher" times, it would C<< ->broadcast >> a condvar once to 1259invoked "watcher" times, it would C<< ->send >> a condvar once to
1140signal the end of this phase. 1260signal the end of this phase.
1141 1261
1142I<destroy> is the time, in microseconds, that it takes to destroy a single 1262I<destroy> is the time, in microseconds, that it takes to destroy a single
1143watcher. 1263watcher.
1144 1264
1397probably even less useful to an attacker than PERL_ANYEVENT_MODEL). 1517probably even less useful to an attacker than PERL_ANYEVENT_MODEL).
1398 1518
1399 1519
1400=head1 SEE ALSO 1520=head1 SEE ALSO
1401 1521
1402Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>, 1522Utility functions: L<AnyEvent::Util>.
1403L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>, 1523
1524Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,
1404L<Event::Lib>, L<Qt>, L<POE>. 1525L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1405 1526
1406Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>, 1527Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1407L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, 1528L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1408L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>, 1529L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1409L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>. 1530L<AnyEvent::Impl::POE>.
1410 1531
1532Non-blocking file handles, sockets, TCP clients and
1533servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.
1534
1535Asynchronous DNS: L<AnyEvent::DNS>.
1536
1537Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,
1538
1411Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. 1539Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1412 1540
1413 1541
1414=head1 AUTHOR 1542=head1 AUTHOR
1415 1543
1416 Marc Lehmann <schmorp@schmorp.de> 1544 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines