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.155 by root, Fri Jun 6 07:07:01 2008 UTC vs.
Revision 1.180 by root, Sat Sep 6 07:00:45 2008 UTC

6 6
7=head1 SYNOPSIS 7=head1 SYNOPSIS
8 8
9 use AnyEvent; 9 use AnyEvent;
10 10
11 my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { 11 my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { ... });
12 ...
13 });
14 12
15 my $w = AnyEvent->timer (after => $seconds, cb => sub { 13 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
14 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
15
16 print AnyEvent->now; # prints current event loop time
17 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
18
19 my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
20
21 my $w = AnyEvent->child (pid => $pid, cb => sub {
22 my ($pid, $status) = @_;
16 ... 23 ...
17 }); 24 });
18 25
19 my $w = AnyEvent->condvar; # stores whether a condition was flagged 26 my $w = AnyEvent->condvar; # stores whether a condition was flagged
20 $w->send; # wake up current and all future recv's 27 $w->send; # wake up current and all future recv's
21 $w->recv; # enters "main loop" till $condvar gets ->send 28 $w->recv; # enters "main loop" till $condvar gets ->send
29 # use a condvar in callback mode:
30 $w->cb (sub { $_[0]->recv });
22 31
23=head1 INTRODUCTION/TUTORIAL 32=head1 INTRODUCTION/TUTORIAL
24 33
25This manpage is mainly a reference manual. If you are interested 34This manpage is mainly a reference manual. If you are interested
26in a tutorial or some gentle introduction, have a look at the 35in a tutorial or some gentle introduction, have a look at the
33 42
34Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of 43Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
35policy> and AnyEvent is I<small and efficient>. 44policy> and AnyEvent is I<small and efficient>.
36 45
37First and foremost, I<AnyEvent is not an event model> itself, it only 46First and foremost, I<AnyEvent is not an event model> itself, it only
38interfaces to whatever event model the main program happens to use in a 47interfaces to whatever event model the main program happens to use, in a
39pragmatic way. For event models and certain classes of immortals alike, 48pragmatic way. For event models and certain classes of immortals alike,
40the statement "there can only be one" is a bitter reality: In general, 49the statement "there can only be one" is a bitter reality: In general,
41only one event loop can be active at the same time in a process. AnyEvent 50only one event loop can be active at the same time in a process. AnyEvent
42helps hiding the differences between those event loops. 51cannot change this, but it can hide the differences between those event
52loops.
43 53
44The goal of AnyEvent is to offer module authors the ability to do event 54The goal of AnyEvent is to offer module authors the ability to do event
45programming (waiting for I/O or timer events) without subscribing to a 55programming (waiting for I/O or timer events) without subscribing to a
46religion, a way of living, and most importantly: without forcing your 56religion, a way of living, and most importantly: without forcing your
47module users into the same thing by forcing them to use the same event 57module users into the same thing by forcing them to use the same event
48model you use. 58model you use.
49 59
50For modules like POE or IO::Async (which is a total misnomer as it is 60For modules like POE or IO::Async (which is a total misnomer as it is
51actually doing all I/O I<synchronously>...), using them in your module is 61actually doing all I/O I<synchronously>...), using them in your module is
52like joining a cult: After you joined, you are dependent on them and you 62like joining a cult: After you joined, you are dependent on them and you
53cannot use anything else, as it is simply incompatible to everything that 63cannot use anything else, as they are simply incompatible to everything
54isn't itself. What's worse, all the potential users of your module are 64that isn't them. What's worse, all the potential users of your
55I<also> forced to use the same event loop you use. 65module are I<also> forced to use the same event loop you use.
56 66
57AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works 67AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
58fine. AnyEvent + Tk works fine etc. etc. but none of these work together 68fine. AnyEvent + Tk works fine etc. etc. but none of these work together
59with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if 69with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if
60your module uses one of those, every user of your module has to use it, 70your module uses one of those, every user of your module has to use it,
61too. But if your module uses AnyEvent, it works transparently with all 71too. But if your module uses AnyEvent, it works transparently with all
62event models it supports (including stuff like POE and IO::Async, as long 72event models it supports (including stuff like IO::Async, as long as those
63as those use one of the supported event loops. It is trivial to add new 73use one of the supported event loops. It is trivial to add new event loops
64event loops to AnyEvent, too, so it is future-proof). 74to AnyEvent, too, so it is future-proof).
65 75
66In addition to being free of having to use I<the one and only true event 76In addition to being free of having to use I<the one and only true event
67model>, AnyEvent also is free of bloat and policy: with POE or similar 77model>, AnyEvent also is free of bloat and policy: with POE or similar
68modules, you get an enormous amount of code and strict rules you have to 78modules, you get an enormous amount of code and strict rules you have to
69follow. AnyEvent, on the other hand, is lean and up to the point, by only 79follow. AnyEvent, on the other hand, is lean and up to the point, by only
152=head2 I/O WATCHERS 162=head2 I/O WATCHERS
153 163
154You can create an I/O watcher by calling the C<< AnyEvent->io >> method 164You can create an I/O watcher by calling the C<< AnyEvent->io >> method
155with the following mandatory key-value pairs as arguments: 165with the following mandatory key-value pairs as arguments:
156 166
157C<fh> the Perl I<file handle> (I<not> file descriptor) to watch 167C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events
158for events. C<poll> must be a string that is either C<r> or C<w>, 168(AnyEvent might or might not keep a reference to this file handle). C<poll>
159which creates a watcher waiting for "r"eadable or "w"ritable events, 169must be a string that is either C<r> or C<w>, which creates a watcher
160respectively. C<cb> is the callback to invoke each time the file handle 170waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the
161becomes ready. 171callback to invoke each time the file handle becomes ready.
162 172
163Although the callback might get passed parameters, their value and 173Although the callback might get passed parameters, their value and
164presence is undefined and you cannot rely on them. Portable AnyEvent 174presence is undefined and you cannot rely on them. Portable AnyEvent
165callbacks cannot use arguments passed to I/O watcher callbacks. 175callbacks cannot use arguments passed to I/O watcher callbacks.
166 176
170 180
171Some event loops issue spurious readyness notifications, so you should 181Some event loops issue spurious readyness notifications, so you should
172always use non-blocking calls when reading/writing from/to your file 182always use non-blocking calls when reading/writing from/to your file
173handles. 183handles.
174 184
175Example:
176
177 # wait for readability of STDIN, then read a line and disable the watcher 185Example: wait for readability of STDIN, then read a line and disable the
186watcher.
187
178 my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { 188 my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
179 chomp (my $input = <STDIN>); 189 chomp (my $input = <STDIN>);
180 warn "read: $input\n"; 190 warn "read: $input\n";
181 undef $w; 191 undef $w;
182 }); 192 });
192 202
193Although the callback might get passed parameters, their value and 203Although the callback might get passed parameters, their value and
194presence is undefined and you cannot rely on them. Portable AnyEvent 204presence is undefined and you cannot rely on them. Portable AnyEvent
195callbacks cannot use arguments passed to time watcher callbacks. 205callbacks cannot use arguments passed to time watcher callbacks.
196 206
197The timer callback will be invoked at most once: if you want a repeating 207The callback will normally be invoked once only. If you specify another
198timer you have to create a new watcher (this is a limitation by both Tk 208parameter, C<interval>, as a strictly positive number (> 0), then the
199and Glib). 209callback will be invoked regularly at that interval (in fractional
210seconds) after the first invocation. If C<interval> is specified with a
211false value, then it is treated as if it were missing.
200 212
201Example: 213The callback will be rescheduled before invoking the callback, but no
214attempt is done to avoid timer drift in most backends, so the interval is
215only approximate.
202 216
203 # fire an event after 7.7 seconds 217Example: fire an event after 7.7 seconds.
218
204 my $w = AnyEvent->timer (after => 7.7, cb => sub { 219 my $w = AnyEvent->timer (after => 7.7, cb => sub {
205 warn "timeout\n"; 220 warn "timeout\n";
206 }); 221 });
207 222
208 # to cancel the timer: 223 # to cancel the timer:
209 undef $w; 224 undef $w;
210 225
211Example 2:
212
213 # fire an event after 0.5 seconds, then roughly every second 226Example 2: fire an event after 0.5 seconds, then roughly every second.
214 my $w;
215 227
216 my $cb = sub {
217 # cancel the old timer while creating a new one
218 $w = AnyEvent->timer (after => 1, cb => $cb); 228 my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
229 warn "timeout\n";
219 }; 230 };
220
221 # start the "loop" by creating the first watcher
222 $w = AnyEvent->timer (after => 0.5, cb => $cb);
223 231
224=head3 TIMING ISSUES 232=head3 TIMING ISSUES
225 233
226There are two ways to handle timers: based on real time (relative, "fire 234There are two ways to handle timers: based on real time (relative, "fire
227in 10 seconds") and based on wallclock time (absolute, "fire at 12 235in 10 seconds") and based on wallclock time (absolute, "fire at 12
305=back 313=back
306 314
307=head2 SIGNAL WATCHERS 315=head2 SIGNAL WATCHERS
308 316
309You can watch for signals using a signal watcher, C<signal> is the signal 317You can watch for signals using a signal watcher, C<signal> is the signal
310I<name> without any C<SIG> prefix, C<cb> is the Perl callback to 318I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
311be invoked whenever a signal occurs. 319callback to be invoked whenever a signal occurs.
312 320
313Although the callback might get passed parameters, their value and 321Although the callback might get passed parameters, their value and
314presence is undefined and you cannot rely on them. Portable AnyEvent 322presence is undefined and you cannot rely on them. Portable AnyEvent
315callbacks cannot use arguments passed to signal watcher callbacks. 323callbacks cannot use arguments passed to signal watcher callbacks.
316 324
382The instrument to do that is called a "condition variable", so called 390The instrument to do that is called a "condition variable", so called
383because they represent a condition that must become true. 391because they represent a condition that must become true.
384 392
385Condition variables can be created by calling the C<< AnyEvent->condvar 393Condition variables can be created by calling the C<< AnyEvent->condvar
386>> method, usually without arguments. The only argument pair allowed is 394>> method, usually without arguments. The only argument pair allowed is
395
387C<cb>, which specifies a callback to be called when the condition variable 396C<cb>, which specifies a callback to be called when the condition variable
388becomes true. 397becomes true, with the condition variable as the first argument (but not
398the results).
389 399
390After creation, the condition variable is "false" until it becomes "true" 400After creation, the condition variable is "false" until it becomes "true"
391by calling the C<send> method (or calling the condition variable as if it 401by calling the C<send> method (or calling the condition variable as if it
392were a callback, read about the caveats in the description for the C<< 402were a callback, read about the caveats in the description for the C<<
393->send >> method). 403->send >> method).
449 459
450 my $done = AnyEvent->condvar; 460 my $done = AnyEvent->condvar;
451 my $delay = AnyEvent->timer (after => 5, cb => $done); 461 my $delay = AnyEvent->timer (after => 5, cb => $done);
452 $done->recv; 462 $done->recv;
453 463
464Example: Imagine an API that returns a condvar and doesn't support
465callbacks. This is how you make a synchronous call, for example from
466the main program:
467
468 use AnyEvent::CouchDB;
469
470 ...
471
472 my @info = $couchdb->info->recv;
473
474And this is how you would just ste a callback to be called whenever the
475results are available:
476
477 $couchdb->info->cb (sub {
478 my @info = $_[0]->recv;
479 });
480
454=head3 METHODS FOR PRODUCERS 481=head3 METHODS FOR PRODUCERS
455 482
456These methods should only be used by the producing side, i.e. the 483These methods should only be used by the producing side, i.e. the
457code/module that eventually sends the signal. Note that it is also 484code/module that eventually sends the signal. Note that it is also
458the producer side which creates the condvar in most cases, but it isn't 485the producer side which creates the condvar in most cases, but it isn't
591=item $bool = $cv->ready 618=item $bool = $cv->ready
592 619
593Returns true when the condition is "true", i.e. whether C<send> or 620Returns true when the condition is "true", i.e. whether C<send> or
594C<croak> have been called. 621C<croak> have been called.
595 622
596=item $cb = $cv->cb ([new callback]) 623=item $cb = $cv->cb ($cb->($cv))
597 624
598This is a mutator function that returns the callback set and optionally 625This is a mutator function that returns the callback set and optionally
599replaces it before doing so. 626replaces it before doing so.
600 627
601The callback will be called when the condition becomes "true", i.e. when 628The callback will be called when the condition becomes "true", i.e. when
738=item L<AnyEvent::Util> 765=item L<AnyEvent::Util>
739 766
740Contains various utility functions that replace often-used but blocking 767Contains various utility functions that replace often-used but blocking
741functions such as C<inet_aton> by event-/callback-based versions. 768functions such as C<inet_aton> by event-/callback-based versions.
742 769
743=item L<AnyEvent::Handle>
744
745Provide read and write buffers and manages watchers for reads and writes.
746
747=item L<AnyEvent::Socket> 770=item L<AnyEvent::Socket>
748 771
749Provides various utility functions for (internet protocol) sockets, 772Provides various utility functions for (internet protocol) sockets,
750addresses and name resolution. Also functions to create non-blocking tcp 773addresses and name resolution. Also functions to create non-blocking tcp
751connections or tcp servers, with IPv6 and SRV record support and more. 774connections or tcp servers, with IPv6 and SRV record support and more.
752 775
776=item L<AnyEvent::Handle>
777
778Provide read and write buffers, manages watchers for reads and writes,
779supports raw and formatted I/O, I/O queued and fully transparent and
780non-blocking SSL/TLS.
781
753=item L<AnyEvent::DNS> 782=item L<AnyEvent::DNS>
754 783
755Provides rich asynchronous DNS resolver capabilities. 784Provides rich asynchronous DNS resolver capabilities.
756 785
757=item L<AnyEvent::HTTP> 786=item L<AnyEvent::HTTP>
765 794
766=item L<AnyEvent::FastPing> 795=item L<AnyEvent::FastPing>
767 796
768The fastest ping in the west. 797The fastest ping in the west.
769 798
799=item L<AnyEvent::DBI>
800
801Executes L<DBI> requests asynchronously in a proxy process.
802
803=item L<AnyEvent::AIO>
804
805Truly asynchronous I/O, should be in the toolbox of every event
806programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
807together.
808
809=item L<AnyEvent::BDB>
810
811Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
812L<BDB> and AnyEvent together.
813
814=item L<AnyEvent::GPSD>
815
816A non-blocking interface to gpsd, a daemon delivering GPS information.
817
818=item L<AnyEvent::IGS>
819
820A non-blocking interface to the Internet Go Server protocol (used by
821L<App::IGS>).
822
770=item L<Net::IRC3> 823=item L<Net::IRC3>
771 824
772AnyEvent based IRC client module family. 825AnyEvent based IRC client module family.
773 826
774=item L<Net::XMPP2> 827=item L<Net::XMPP2>
786 839
787=item L<Coro> 840=item L<Coro>
788 841
789Has special support for AnyEvent via L<Coro::AnyEvent>. 842Has special support for AnyEvent via L<Coro::AnyEvent>.
790 843
791=item L<AnyEvent::AIO>, L<IO::AIO>
792
793Truly asynchronous I/O, should be in the toolbox of every event
794programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
795together.
796
797=item L<AnyEvent::BDB>, L<BDB>
798
799Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
800IO::AIO and AnyEvent together.
801
802=item L<IO::Lambda> 844=item L<IO::Lambda>
803 845
804The lambda approach to I/O - don't ask, look there. Can use AnyEvent. 846The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
805 847
806=back 848=back
808=cut 850=cut
809 851
810package AnyEvent; 852package AnyEvent;
811 853
812no warnings; 854no warnings;
813use strict; 855use strict qw(vars subs);
814 856
815use Carp; 857use Carp;
816 858
817our $VERSION = 4.14; 859our $VERSION = 4.233;
818our $MODEL; 860our $MODEL;
819 861
820our $AUTOLOAD; 862our $AUTOLOAD;
821our @ISA; 863our @ISA;
822 864
925 $MODEL 967 $MODEL
926 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib."; 968 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
927 } 969 }
928 } 970 }
929 971
972 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
973
930 unshift @ISA, $MODEL; 974 unshift @ISA, $MODEL;
931 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 975
976 require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
932 977
933 (shift @post_detect)->() while @post_detect; 978 (shift @post_detect)->() while @post_detect;
934 } 979 }
935 980
936 $MODEL 981 $MODEL
946 991
947 my $class = shift; 992 my $class = shift;
948 $class->$func (@_); 993 $class->$func (@_);
949} 994}
950 995
996# utility function to dup a filehandle. this is used by many backends
997# to support binding more than one watcher per filehandle (they usually
998# allow only one watcher per fd, so we dup it to get a different one).
999sub _dupfh($$$$) {
1000 my ($poll, $fh, $r, $w) = @_;
1001
1002 require Fcntl;
1003
1004 # cygwin requires the fh mode to be matching, unix doesn't
1005 my ($rw, $mode) = $poll eq "r" ? ($r, "<")
1006 : $poll eq "w" ? ($w, ">")
1007 : Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1008
1009 open my $fh2, "$mode&" . fileno $fh
1010 or die "cannot dup() filehandle: $!";
1011
1012 # we assume CLOEXEC is already set by perl in all important cases
1013
1014 ($fh2, $rw)
1015}
1016
951package AnyEvent::Base; 1017package AnyEvent::Base;
952 1018
953# default implementation for now and time 1019# default implementation for now and time
954 1020
955use Time::HiRes (); 1021BEGIN {
1022 if (eval "use Time::HiRes (); time (); 1") {
1023 *_time = \&Time::HiRes::time;
1024 # if (eval "use POSIX (); (POSIX::times())...
1025 } else {
1026 *_time = \&CORE::time; # epic fail
1027 }
1028}
956 1029
957sub time { Time::HiRes::time } 1030sub time { _time }
958sub now { Time::HiRes::time } 1031sub now { _time }
959 1032
960# default implementation for ->condvar 1033# default implementation for ->condvar
961 1034
962sub condvar { 1035sub condvar {
963 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: 1036 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
984sub AnyEvent::Base::Signal::DESTROY { 1057sub AnyEvent::Base::Signal::DESTROY {
985 my ($signal, $cb) = @{$_[0]}; 1058 my ($signal, $cb) = @{$_[0]};
986 1059
987 delete $SIG_CB{$signal}{$cb}; 1060 delete $SIG_CB{$signal}{$cb};
988 1061
989 $SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} }; 1062 delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
990} 1063}
991 1064
992# default implementation for ->child 1065# default implementation for ->child
993 1066
994our %PID_CB; 1067our %PID_CB;
1102 1175
1103# undocumented/compatibility with pre-3.4 1176# undocumented/compatibility with pre-3.4
1104*broadcast = \&send; 1177*broadcast = \&send;
1105*wait = \&_wait; 1178*wait = \&_wait;
1106 1179
1180=head1 ERROR AND EXCEPTION HANDLING
1181
1182In general, AnyEvent does not do any error handling - it relies on the
1183caller to do that if required. The L<AnyEvent::Strict> module (see also
1184the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
1185checking of all AnyEvent methods, however, which is highly useful during
1186development.
1187
1188As for exception handling (i.e. runtime errors and exceptions thrown while
1189executing a callback), this is not only highly event-loop specific, but
1190also not in any way wrapped by this module, as this is the job of the main
1191program.
1192
1193The pure perl event loop simply re-throws the exception (usually
1194within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
1195$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
1196so on.
1197
1198=head1 ENVIRONMENT VARIABLES
1199
1200The following environment variables are used by this module or its
1201submodules:
1202
1203=over 4
1204
1205=item C<PERL_ANYEVENT_VERBOSE>
1206
1207By default, AnyEvent will be completely silent except in fatal
1208conditions. You can set this environment variable to make AnyEvent more
1209talkative.
1210
1211When set to C<1> or higher, causes AnyEvent to warn about unexpected
1212conditions, such as not being able to load the event model specified by
1213C<PERL_ANYEVENT_MODEL>.
1214
1215When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1216model it chooses.
1217
1218=item C<PERL_ANYEVENT_STRICT>
1219
1220AnyEvent does not do much argument checking by default, as thorough
1221argument checking is very costly. Setting this variable to a true value
1222will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1223check the arguments passed to most method calls. If it finds any problems
1224it will croak.
1225
1226In other words, enables "strict" mode.
1227
1228Unlike C<use strict>, it is definitely recommended ot keep it off in
1229production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while
1230developing programs can be very useful, however.
1231
1232=item C<PERL_ANYEVENT_MODEL>
1233
1234This can be used to specify the event model to be used by AnyEvent, before
1235auto detection and -probing kicks in. It must be a string consisting
1236entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1237and the resulting module name is loaded and if the load was successful,
1238used as event model. If it fails to load AnyEvent will proceed with
1239auto detection and -probing.
1240
1241This functionality might change in future versions.
1242
1243For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1244could start your program like this:
1245
1246 PERL_ANYEVENT_MODEL=Perl perl ...
1247
1248=item C<PERL_ANYEVENT_PROTOCOLS>
1249
1250Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1251for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1252of auto probing).
1253
1254Must be set to a comma-separated list of protocols or address families,
1255current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1256used, and preference will be given to protocols mentioned earlier in the
1257list.
1258
1259This variable can effectively be used for denial-of-service attacks
1260against local programs (e.g. when setuid), although the impact is likely
1261small, as the program has to handle connection errors already-
1262
1263Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1264but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1265- only support IPv4, never try to resolve or contact IPv6
1266addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1267IPv6, but prefer IPv6 over IPv4.
1268
1269=item C<PERL_ANYEVENT_EDNS0>
1270
1271Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1272for DNS. This extension is generally useful to reduce DNS traffic, but
1273some (broken) firewalls drop such DNS packets, which is why it is off by
1274default.
1275
1276Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1277EDNS0 in its DNS requests.
1278
1279=item C<PERL_ANYEVENT_MAX_FORKS>
1280
1281The maximum number of child processes that C<AnyEvent::Util::fork_call>
1282will create in parallel.
1283
1284=back
1285
1107=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE 1286=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1108 1287
1109This is an advanced topic that you do not normally need to use AnyEvent in 1288This is an advanced topic that you do not normally need to use AnyEvent in
1110a module. This section is only of use to event loop authors who want to 1289a module. This section is only of use to event loop authors who want to
1111provide AnyEvent compatibility. 1290provide AnyEvent compatibility.
1144 1323
1145I<rxvt-unicode> also cheats a bit by not providing blocking access to 1324I<rxvt-unicode> also cheats a bit by not providing blocking access to
1146condition variables: code blocking while waiting for a condition will 1325condition variables: code blocking while waiting for a condition will
1147C<die>. This still works with most modules/usages, and blocking calls must 1326C<die>. This still works with most modules/usages, and blocking calls must
1148not be done in an interactive application, so it makes sense. 1327not be done in an interactive application, so it makes sense.
1149
1150=head1 ENVIRONMENT VARIABLES
1151
1152The following environment variables are used by this module:
1153
1154=over 4
1155
1156=item C<PERL_ANYEVENT_VERBOSE>
1157
1158By default, AnyEvent will be completely silent except in fatal
1159conditions. You can set this environment variable to make AnyEvent more
1160talkative.
1161
1162When set to C<1> or higher, causes AnyEvent to warn about unexpected
1163conditions, such as not being able to load the event model specified by
1164C<PERL_ANYEVENT_MODEL>.
1165
1166When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1167model it chooses.
1168
1169=item C<PERL_ANYEVENT_MODEL>
1170
1171This can be used to specify the event model to be used by AnyEvent, before
1172auto detection and -probing kicks in. It must be a string consisting
1173entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1174and the resulting module name is loaded and if the load was successful,
1175used as event model. If it fails to load AnyEvent will proceed with
1176auto detection and -probing.
1177
1178This functionality might change in future versions.
1179
1180For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1181could start your program like this:
1182
1183 PERL_ANYEVENT_MODEL=Perl perl ...
1184
1185=item C<PERL_ANYEVENT_PROTOCOLS>
1186
1187Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1188for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1189of auto probing).
1190
1191Must be set to a comma-separated list of protocols or address families,
1192current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1193used, and preference will be given to protocols mentioned earlier in the
1194list.
1195
1196This variable can effectively be used for denial-of-service attacks
1197against local programs (e.g. when setuid), although the impact is likely
1198small, as the program has to handle connection errors already-
1199
1200Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1201but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1202- only support IPv4, never try to resolve or contact IPv6
1203addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1204IPv6, but prefer IPv6 over IPv4.
1205
1206=item C<PERL_ANYEVENT_EDNS0>
1207
1208Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1209for DNS. This extension is generally useful to reduce DNS traffic, but
1210some (broken) firewalls drop such DNS packets, which is why it is off by
1211default.
1212
1213Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1214EDNS0 in its DNS requests.
1215
1216=item C<PERL_ANYEVENT_MAX_FORKS>
1217
1218The maximum number of child processes that C<AnyEvent::Util::fork_call>
1219will create in parallel.
1220
1221=back
1222 1328
1223=head1 EXAMPLE PROGRAM 1329=head1 EXAMPLE PROGRAM
1224 1330
1225The following program uses an I/O watcher to read data from STDIN, a timer 1331The following program uses an I/O watcher to read data from STDIN, a timer
1226to display a message once per second, and a condition variable to quit the 1332to display a message once per second, and a condition variable to quit the
1669 1775
1670 use AnyEvent; 1776 use AnyEvent;
1671 1777
1672Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can 1778Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1673be used to probe what backend is used and gain other information (which is 1779be used to probe what backend is used and gain other information (which is
1674probably even less useful to an attacker than PERL_ANYEVENT_MODEL). 1780probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1781$ENV{PERL_ANYEGENT_STRICT}.
1782
1783
1784=head1 BUGS
1785
1786Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1787to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1788and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1789mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
1790pronounced).
1675 1791
1676 1792
1677=head1 SEE ALSO 1793=head1 SEE ALSO
1678 1794
1679Utility functions: L<AnyEvent::Util>. 1795Utility functions: L<AnyEvent::Util>.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines