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 | |
… | |
… | |
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->send; # wake up current and all future recv's |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
|
|
22 | |
|
|
23 | =head1 INTRODUCTION/TUTORIAL |
|
|
24 | |
|
|
25 | This manpage is mainly a reference manual. If you are interested |
|
|
26 | in a tutorial or some gentle introduction, have a look at the |
|
|
27 | L<AnyEvent::Intro> manpage. |
22 | |
28 | |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
29 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
24 | |
30 | |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
31 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
26 | nowadays. So what is different about AnyEvent? |
32 | nowadays. So what is different about AnyEvent? |
… | |
… | |
48 | isn't itself. What's worse, all the potential users of your module are |
54 | isn't itself. What's worse, all the potential users of your module are |
49 | I<also> forced to use the same event loop you use. |
55 | I<also> forced to use the same event loop you use. |
50 | |
56 | |
51 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
57 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
52 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
58 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
53 | with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if |
59 | with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if |
54 | your module uses one of those, every user of your module has to use it, |
60 | your module uses one of those, every user of your module has to use it, |
55 | too. But if your module uses AnyEvent, it works transparently with all |
61 | too. But if your module uses AnyEvent, it works transparently with all |
56 | event models it supports (including stuff like POE and IO::Async, as long |
62 | event models it supports (including stuff like POE and IO::Async, as long |
57 | as those use one of the supported event loops. It is trivial to add new |
63 | as those use one of the supported event loops. It is trivial to add new |
58 | event loops to AnyEvent, too, so it is future-proof). |
64 | event loops to AnyEvent, too, so it is future-proof). |
… | |
… | |
62 | modules, you get an enormous amount of code and strict rules you have to |
68 | modules, you get an enormous amount of code and strict rules you have to |
63 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
69 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
64 | offering the functionality that is necessary, in as thin as a wrapper as |
70 | offering the functionality that is necessary, in as thin as a wrapper as |
65 | technically possible. |
71 | technically possible. |
66 | |
72 | |
|
|
73 | Of course, AnyEvent comes with a big (and fully optional!) toolbox |
|
|
74 | of useful functionality, such as an asynchronous DNS resolver, 100% |
|
|
75 | non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms |
|
|
76 | such as Windows) and lots of real-world knowledge and workarounds for |
|
|
77 | platform bugs and differences. |
|
|
78 | |
67 | Of course, if you want lots of policy (this can arguably be somewhat |
79 | Now, if you I<do want> lots of policy (this can arguably be somewhat |
68 | useful) and you want to force your users to use the one and only event |
80 | useful) and you want to force your users to use the one and only event |
69 | model, you should I<not> use this module. |
81 | model, you should I<not> use this module. |
70 | |
82 | |
71 | =head1 DESCRIPTION |
83 | =head1 DESCRIPTION |
72 | |
84 | |
… | |
… | |
102 | starts using it, all bets are off. Maybe you should tell their authors to |
114 | starts using it, all bets are off. Maybe you should tell their authors to |
103 | use AnyEvent so their modules work together with others seamlessly... |
115 | use AnyEvent so their modules work together with others seamlessly... |
104 | |
116 | |
105 | The pure-perl implementation of AnyEvent is called |
117 | The pure-perl implementation of AnyEvent is called |
106 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
118 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
107 | explicitly. |
119 | explicitly and enjoy the high availability of that event loop :) |
108 | |
120 | |
109 | =head1 WATCHERS |
121 | =head1 WATCHERS |
110 | |
122 | |
111 | AnyEvent has the central concept of a I<watcher>, which is an object that |
123 | AnyEvent has the central concept of a I<watcher>, which is an object that |
112 | stores relevant data for each kind of event you are waiting for, such as |
124 | stores relevant data for each kind of event you are waiting for, such as |
… | |
… | |
126 | Many watchers either are used with "recursion" (repeating timers for |
138 | Many watchers either are used with "recursion" (repeating timers for |
127 | example), or need to refer to their watcher object in other ways. |
139 | example), or need to refer to their watcher object in other ways. |
128 | |
140 | |
129 | An any way to achieve that is this pattern: |
141 | An any way to achieve that is this pattern: |
130 | |
142 | |
131 | my $w; $w = AnyEvent->type (arg => value ..., cb => sub { |
143 | my $w; $w = AnyEvent->type (arg => value ..., cb => sub { |
132 | # you can use $w here, for example to undef it |
144 | # you can use $w here, for example to undef it |
133 | undef $w; |
145 | undef $w; |
134 | }); |
146 | }); |
135 | |
147 | |
136 | Note that C<my $w; $w => combination. This is necessary because in Perl, |
148 | Note that C<my $w; $w => combination. This is necessary because in Perl, |
137 | my variables are only visible after the statement in which they are |
149 | my variables are only visible after the statement in which they are |
138 | declared. |
150 | declared. |
139 | |
151 | |
… | |
… | |
227 | timers. |
239 | timers. |
228 | |
240 | |
229 | AnyEvent always prefers relative timers, if available, matching the |
241 | AnyEvent always prefers relative timers, if available, matching the |
230 | AnyEvent API. |
242 | AnyEvent API. |
231 | |
243 | |
|
|
244 | AnyEvent has two additional methods that return the "current time": |
|
|
245 | |
|
|
246 | =over 4 |
|
|
247 | |
|
|
248 | =item AnyEvent->time |
|
|
249 | |
|
|
250 | This returns the "current wallclock time" as a fractional number of |
|
|
251 | seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time> |
|
|
252 | return, and the result is guaranteed to be compatible with those). |
|
|
253 | |
|
|
254 | It progresses independently of any event loop processing, i.e. each call |
|
|
255 | will check the system clock, which usually gets updated frequently. |
|
|
256 | |
|
|
257 | =item AnyEvent->now |
|
|
258 | |
|
|
259 | This also returns the "current wallclock time", but unlike C<time>, above, |
|
|
260 | this value might change only once per event loop iteration, depending on |
|
|
261 | the event loop (most return the same time as C<time>, above). This is the |
|
|
262 | time that AnyEvent's timers get scheduled against. |
|
|
263 | |
|
|
264 | I<In almost all cases (in all cases if you don't care), this is the |
|
|
265 | function to call when you want to know the current time.> |
|
|
266 | |
|
|
267 | This function is also often faster then C<< AnyEvent->time >>, and |
|
|
268 | thus the preferred method if you want some timestamp (for example, |
|
|
269 | L<AnyEvent::Handle> uses this to update it's activity timeouts). |
|
|
270 | |
|
|
271 | The rest of this section is only of relevance if you try to be very exact |
|
|
272 | with your timing, you can skip it without bad conscience. |
|
|
273 | |
|
|
274 | For a practical example of when these times differ, consider L<Event::Lib> |
|
|
275 | and L<EV> and the following set-up: |
|
|
276 | |
|
|
277 | The event loop is running and has just invoked one of your callback at |
|
|
278 | time=500 (assume no other callbacks delay processing). In your callback, |
|
|
279 | you wait a second by executing C<sleep 1> (blocking the process for a |
|
|
280 | second) and then (at time=501) you create a relative timer that fires |
|
|
281 | after three seconds. |
|
|
282 | |
|
|
283 | With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will |
|
|
284 | both return C<501>, because that is the current time, and the timer will |
|
|
285 | be scheduled to fire at time=504 (C<501> + C<3>). |
|
|
286 | |
|
|
287 | With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current |
|
|
288 | time), but C<< AnyEvent->now >> returns C<500>, as that is the time the |
|
|
289 | last event processing phase started. With L<EV>, your timer gets scheduled |
|
|
290 | to run at time=503 (C<500> + C<3>). |
|
|
291 | |
|
|
292 | In one sense, L<Event::Lib> is more exact, as it uses the current time |
|
|
293 | regardless of any delays introduced by event processing. However, most |
|
|
294 | callbacks do not expect large delays in processing, so this causes a |
|
|
295 | higher drift (and a lot more system calls to get the current time). |
|
|
296 | |
|
|
297 | In another sense, L<EV> is more exact, as your timer will be scheduled at |
|
|
298 | the same time, regardless of how long event processing actually took. |
|
|
299 | |
|
|
300 | In either case, if you care (and in most cases, you don't), then you |
|
|
301 | can get whatever behaviour you want with any event loop, by taking the |
|
|
302 | difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into |
|
|
303 | account. |
|
|
304 | |
|
|
305 | =back |
|
|
306 | |
232 | =head2 SIGNAL WATCHERS |
307 | =head2 SIGNAL WATCHERS |
233 | |
308 | |
234 | You can watch for signals using a signal watcher, C<signal> is the signal |
309 | You can watch for signals using a signal watcher, C<signal> is the signal |
235 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
310 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
236 | be invoked whenever a signal occurs. |
311 | be invoked whenever a signal occurs. |
… | |
… | |
277 | AnyEvent program, you I<have> to create at least one watcher before you |
352 | AnyEvent program, you I<have> to create at least one watcher before you |
278 | C<fork> the child (alternatively, you can call C<AnyEvent::detect>). |
353 | C<fork> the child (alternatively, you can call C<AnyEvent::detect>). |
279 | |
354 | |
280 | Example: fork a process and wait for it |
355 | Example: fork a process and wait for it |
281 | |
356 | |
282 | my $done = AnyEvent->condvar; |
357 | my $done = AnyEvent->condvar; |
283 | |
358 | |
284 | my $pid = fork or exit 5; |
359 | my $pid = fork or exit 5; |
285 | |
360 | |
286 | my $w = AnyEvent->child ( |
361 | my $w = AnyEvent->child ( |
287 | pid => $pid, |
362 | pid => $pid, |
288 | cb => sub { |
363 | cb => sub { |
289 | my ($pid, $status) = @_; |
364 | my ($pid, $status) = @_; |
290 | warn "pid $pid exited with status $status"; |
365 | warn "pid $pid exited with status $status"; |
291 | $done->send; |
366 | $done->send; |
292 | }, |
367 | }, |
293 | ); |
368 | ); |
294 | |
369 | |
295 | # do something else, then wait for process exit |
370 | # do something else, then wait for process exit |
296 | $done->recv; |
371 | $done->recv; |
297 | |
372 | |
298 | =head2 CONDITION VARIABLES |
373 | =head2 CONDITION VARIABLES |
299 | |
374 | |
300 | If you are familiar with some event loops you will know that all of them |
375 | If you are familiar with some event loops you will know that all of them |
301 | require you to run some blocking "loop", "run" or similar function that |
376 | require you to run some blocking "loop", "run" or similar function that |
… | |
… | |
312 | C<cb>, which specifies a callback to be called when the condition variable |
387 | C<cb>, which specifies a callback to be called when the condition variable |
313 | becomes true. |
388 | becomes true. |
314 | |
389 | |
315 | After creation, the condition variable is "false" until it becomes "true" |
390 | After creation, the condition variable is "false" until it becomes "true" |
316 | by calling the C<send> method (or calling the condition variable as if it |
391 | by calling the C<send> method (or calling the condition variable as if it |
317 | were a callback). |
392 | were a callback, read about the caveats in the description for the C<< |
|
|
393 | ->send >> method). |
318 | |
394 | |
319 | Condition variables are similar to callbacks, except that you can |
395 | Condition variables are similar to callbacks, except that you can |
320 | optionally wait for them. They can also be called merge points - points |
396 | optionally wait for them. They can also be called merge points - points |
321 | in time where multiple outstanding events have been processed. And yet |
397 | in time where multiple outstanding events have been processed. And yet |
322 | another way to call them is transactions - each condition variable can be |
398 | another way to call them is transactions - each condition variable can be |
… | |
… | |
394 | immediately from within send. |
470 | immediately from within send. |
395 | |
471 | |
396 | Any arguments passed to the C<send> call will be returned by all |
472 | Any arguments passed to the C<send> call will be returned by all |
397 | future C<< ->recv >> calls. |
473 | future C<< ->recv >> calls. |
398 | |
474 | |
399 | Condition variables are overloaded so one can call them directly (as a |
475 | Condition variables are overloaded so one can call them directly |
400 | code reference). Calling them directly is the same as calling C<send>. |
476 | (as a code reference). Calling them directly is the same as calling |
|
|
477 | C<send>. Note, however, that many C-based event loops do not handle |
|
|
478 | overloading, so as tempting as it may be, passing a condition variable |
|
|
479 | instead of a callback does not work. Both the pure perl and EV loops |
|
|
480 | support overloading, however, as well as all functions that use perl to |
|
|
481 | invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for |
|
|
482 | example). |
401 | |
483 | |
402 | =item $cv->croak ($error) |
484 | =item $cv->croak ($error) |
403 | |
485 | |
404 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
486 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
405 | C<Carp::croak> with the given error message/object/scalar. |
487 | C<Carp::croak> with the given error message/object/scalar. |
… | |
… | |
515 | |
597 | |
516 | This is a mutator function that returns the callback set and optionally |
598 | This is a mutator function that returns the callback set and optionally |
517 | replaces it before doing so. |
599 | replaces it before doing so. |
518 | |
600 | |
519 | The callback will be called when the condition becomes "true", i.e. when |
601 | The callback will be called when the condition becomes "true", i.e. when |
520 | C<send> or C<croak> are called. Calling C<recv> inside the callback |
602 | C<send> or C<croak> are called, with the only argument being the condition |
521 | or at any later time is guaranteed not to block. |
603 | variable itself. Calling C<recv> inside the callback or at any later time |
|
|
604 | is guaranteed not to block. |
522 | |
605 | |
523 | =back |
606 | =back |
524 | |
607 | |
525 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
608 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
526 | |
609 | |
… | |
… | |
669 | |
752 | |
670 | =item L<AnyEvent::DNS> |
753 | =item L<AnyEvent::DNS> |
671 | |
754 | |
672 | Provides rich asynchronous DNS resolver capabilities. |
755 | Provides rich asynchronous DNS resolver capabilities. |
673 | |
756 | |
|
|
757 | =item L<AnyEvent::HTTP> |
|
|
758 | |
|
|
759 | A simple-to-use HTTP library that is capable of making a lot of concurrent |
|
|
760 | HTTP requests. |
|
|
761 | |
674 | =item L<AnyEvent::HTTPD> |
762 | =item L<AnyEvent::HTTPD> |
675 | |
763 | |
676 | Provides a simple web application server framework. |
764 | Provides a simple web application server framework. |
677 | |
765 | |
678 | =item L<AnyEvent::FastPing> |
766 | =item L<AnyEvent::FastPing> |
… | |
… | |
724 | no warnings; |
812 | no warnings; |
725 | use strict; |
813 | use strict; |
726 | |
814 | |
727 | use Carp; |
815 | use Carp; |
728 | |
816 | |
729 | our $VERSION = '4.03'; |
817 | our $VERSION = 4.14; |
730 | our $MODEL; |
818 | our $MODEL; |
731 | |
819 | |
732 | our $AUTOLOAD; |
820 | our $AUTOLOAD; |
733 | our @ISA; |
821 | our @ISA; |
734 | |
822 | |
|
|
823 | our @REGISTRY; |
|
|
824 | |
|
|
825 | our $WIN32; |
|
|
826 | |
|
|
827 | BEGIN { |
|
|
828 | my $win32 = ! ! ($^O =~ /mswin32/i); |
|
|
829 | eval "sub WIN32(){ $win32 }"; |
|
|
830 | } |
|
|
831 | |
735 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
832 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
736 | |
833 | |
737 | our @REGISTRY; |
834 | our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred |
738 | |
|
|
739 | our %PROTOCOL; # (ipv4|ipv6) => (1|2) |
|
|
740 | |
835 | |
741 | { |
836 | { |
742 | my $idx; |
837 | my $idx; |
743 | $PROTOCOL{$_} = ++$idx |
838 | $PROTOCOL{$_} = ++$idx |
|
|
839 | for reverse split /\s*,\s*/, |
744 | for split /\s*,\s*/, $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
840 | $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
745 | } |
841 | } |
746 | |
842 | |
747 | my @models = ( |
843 | my @models = ( |
748 | [EV:: => AnyEvent::Impl::EV::], |
844 | [EV:: => AnyEvent::Impl::EV::], |
749 | [Event:: => AnyEvent::Impl::Event::], |
845 | [Event:: => AnyEvent::Impl::Event::], |
750 | [Tk:: => AnyEvent::Impl::Tk::], |
|
|
751 | [Wx:: => AnyEvent::Impl::POE::], |
|
|
752 | [Prima:: => AnyEvent::Impl::POE::], |
|
|
753 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
846 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
754 | # everything below here will not be autoprobed as the pureperl backend should work everywhere |
847 | # everything below here will not be autoprobed |
755 | [Glib:: => AnyEvent::Impl::Glib::], |
848 | # as the pureperl backend should work everywhere |
|
|
849 | # and is usually faster |
|
|
850 | [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles |
|
|
851 | [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers |
756 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
852 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
757 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
853 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
758 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
854 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
|
|
855 | [Wx:: => AnyEvent::Impl::POE::], |
|
|
856 | [Prima:: => AnyEvent::Impl::POE::], |
759 | ); |
857 | ); |
760 | |
858 | |
761 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
859 | our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); |
762 | |
860 | |
763 | our @post_detect; |
861 | our @post_detect; |
764 | |
862 | |
765 | sub post_detect(&) { |
863 | sub post_detect(&) { |
766 | my ($cb) = @_; |
864 | my ($cb) = @_; |
… | |
… | |
783 | } |
881 | } |
784 | |
882 | |
785 | sub detect() { |
883 | sub detect() { |
786 | unless ($MODEL) { |
884 | unless ($MODEL) { |
787 | no strict 'refs'; |
885 | no strict 'refs'; |
|
|
886 | local $SIG{__DIE__}; |
788 | |
887 | |
789 | if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { |
888 | if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { |
790 | my $model = "AnyEvent::Impl::$1"; |
889 | my $model = "AnyEvent::Impl::$1"; |
791 | if (eval "require $model") { |
890 | if (eval "require $model") { |
792 | $MODEL = $model; |
891 | $MODEL = $model; |
… | |
… | |
849 | $class->$func (@_); |
948 | $class->$func (@_); |
850 | } |
949 | } |
851 | |
950 | |
852 | package AnyEvent::Base; |
951 | package AnyEvent::Base; |
853 | |
952 | |
|
|
953 | # default implementation for now and time |
|
|
954 | |
|
|
955 | use Time::HiRes (); |
|
|
956 | |
|
|
957 | sub time { Time::HiRes::time } |
|
|
958 | sub now { Time::HiRes::time } |
|
|
959 | |
854 | # default implementation for ->condvar |
960 | # default implementation for ->condvar |
855 | |
961 | |
856 | sub condvar { |
962 | sub condvar { |
857 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
963 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
858 | } |
964 | } |
… | |
… | |
915 | or Carp::croak "required option 'pid' is missing"; |
1021 | or Carp::croak "required option 'pid' is missing"; |
916 | |
1022 | |
917 | $PID_CB{$pid}{$arg{cb}} = $arg{cb}; |
1023 | $PID_CB{$pid}{$arg{cb}} = $arg{cb}; |
918 | |
1024 | |
919 | unless ($WNOHANG) { |
1025 | unless ($WNOHANG) { |
920 | $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1; |
1026 | $WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1; |
921 | } |
1027 | } |
922 | |
1028 | |
923 | unless ($CHLD_W) { |
1029 | unless ($CHLD_W) { |
924 | $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); |
1030 | $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); |
925 | # child could be a zombie already, so make at least one round |
1031 | # child could be a zombie already, so make at least one round |
… | |
… | |
1072 | This functionality might change in future versions. |
1178 | This functionality might change in future versions. |
1073 | |
1179 | |
1074 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
1180 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
1075 | could start your program like this: |
1181 | could start your program like this: |
1076 | |
1182 | |
1077 | PERL_ANYEVENT_MODEL=Perl perl ... |
1183 | PERL_ANYEVENT_MODEL=Perl perl ... |
1078 | |
1184 | |
1079 | =item C<PERL_ANYEVENT_PROTOCOLS> |
1185 | =item C<PERL_ANYEVENT_PROTOCOLS> |
1080 | |
1186 | |
1081 | Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences |
1187 | Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences |
1082 | for IPv4 or IPv6. The default is unspecified (and might change, or be the result |
1188 | for IPv4 or IPv6. The default is unspecified (and might change, or be the result |
… | |
… | |
1104 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1210 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1105 | default. |
1211 | default. |
1106 | |
1212 | |
1107 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1213 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1108 | EDNS0 in its DNS requests. |
1214 | EDNS0 in its DNS requests. |
|
|
1215 | |
|
|
1216 | =item C<PERL_ANYEVENT_MAX_FORKS> |
|
|
1217 | |
|
|
1218 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
|
|
1219 | will create in parallel. |
1109 | |
1220 | |
1110 | =back |
1221 | =back |
1111 | |
1222 | |
1112 | =head1 EXAMPLE PROGRAM |
1223 | =head1 EXAMPLE PROGRAM |
1113 | |
1224 | |
… | |
… | |
1552 | specified in the variable. |
1663 | specified in the variable. |
1553 | |
1664 | |
1554 | You can make AnyEvent completely ignore this variable by deleting it |
1665 | You can make AnyEvent completely ignore this variable by deleting it |
1555 | before the first watcher gets created, e.g. with a C<BEGIN> block: |
1666 | before the first watcher gets created, e.g. with a C<BEGIN> block: |
1556 | |
1667 | |
1557 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1668 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1558 | |
1669 | |
1559 | use AnyEvent; |
1670 | use AnyEvent; |
1560 | |
1671 | |
1561 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
1672 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
1562 | be used to probe what backend is used and gain other information (which is |
1673 | be used to probe what backend is used and gain other information (which is |
1563 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
1674 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
|
|
1675 | |
|
|
1676 | |
|
|
1677 | =head1 BUGS |
|
|
1678 | |
|
|
1679 | Perl 5.8 has numerous memleaks that sometimes hit this module and are hard |
|
|
1680 | to work around. If you suffer from memleaks, first upgrade to Perl 5.10 |
|
|
1681 | and check wether the leaks still show up. (Perl 5.10.0 has other annoying |
|
|
1682 | mamleaks, such as leaking on C<map> and C<grep> but it is usually not as |
|
|
1683 | pronounced). |
1564 | |
1684 | |
1565 | |
1685 | |
1566 | =head1 SEE ALSO |
1686 | =head1 SEE ALSO |
1567 | |
1687 | |
1568 | Utility functions: L<AnyEvent::Util>. |
1688 | Utility functions: L<AnyEvent::Util>. |
… | |
… | |
1585 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
1705 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
1586 | |
1706 | |
1587 | |
1707 | |
1588 | =head1 AUTHOR |
1708 | =head1 AUTHOR |
1589 | |
1709 | |
1590 | Marc Lehmann <schmorp@schmorp.de> |
1710 | Marc Lehmann <schmorp@schmorp.de> |
1591 | http://home.schmorp.de/ |
1711 | http://home.schmorp.de/ |
1592 | |
1712 | |
1593 | =cut |
1713 | =cut |
1594 | |
1714 | |
1595 | 1 |
1715 | 1 |
1596 | |
1716 | |