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 | |
… | |
… | |
158 | |
170 | |
159 | Some event loops issue spurious readyness notifications, so you should |
171 | Some event loops issue spurious readyness notifications, so you should |
160 | always use non-blocking calls when reading/writing from/to your file |
172 | always use non-blocking calls when reading/writing from/to your file |
161 | handles. |
173 | handles. |
162 | |
174 | |
163 | Example: |
|
|
164 | |
|
|
165 | # wait for readability of STDIN, then read a line and disable the watcher |
175 | Example: wait for readability of STDIN, then read a line and disable the |
|
|
176 | watcher. |
|
|
177 | |
166 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
178 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
167 | chomp (my $input = <STDIN>); |
179 | chomp (my $input = <STDIN>); |
168 | warn "read: $input\n"; |
180 | warn "read: $input\n"; |
169 | undef $w; |
181 | undef $w; |
170 | }); |
182 | }); |
… | |
… | |
180 | |
192 | |
181 | Although the callback might get passed parameters, their value and |
193 | Although the callback might get passed parameters, their value and |
182 | presence is undefined and you cannot rely on them. Portable AnyEvent |
194 | presence is undefined and you cannot rely on them. Portable AnyEvent |
183 | callbacks cannot use arguments passed to time watcher callbacks. |
195 | callbacks cannot use arguments passed to time watcher callbacks. |
184 | |
196 | |
185 | The timer callback will be invoked at most once: if you want a repeating |
197 | The callback will normally be invoked once only. If you specify another |
186 | timer you have to create a new watcher (this is a limitation by both Tk |
198 | parameter, C<interval>, as a strictly positive number (> 0), then the |
187 | and Glib). |
199 | callback will be invoked regularly at that interval (in fractional |
|
|
200 | seconds) after the first invocation. If C<interval> is specified with a |
|
|
201 | false value, then it is treated as if it were missing. |
188 | |
202 | |
189 | Example: |
203 | The callback will be rescheduled before invoking the callback, but no |
|
|
204 | attempt is done to avoid timer drift in most backends, so the interval is |
|
|
205 | only approximate. |
190 | |
206 | |
191 | # fire an event after 7.7 seconds |
207 | Example: fire an event after 7.7 seconds. |
|
|
208 | |
192 | my $w = AnyEvent->timer (after => 7.7, cb => sub { |
209 | my $w = AnyEvent->timer (after => 7.7, cb => sub { |
193 | warn "timeout\n"; |
210 | warn "timeout\n"; |
194 | }); |
211 | }); |
195 | |
212 | |
196 | # to cancel the timer: |
213 | # to cancel the timer: |
197 | undef $w; |
214 | undef $w; |
198 | |
215 | |
199 | Example 2: |
|
|
200 | |
|
|
201 | # fire an event after 0.5 seconds, then roughly every second |
216 | Example 2: fire an event after 0.5 seconds, then roughly every second. |
202 | my $w; |
|
|
203 | |
217 | |
204 | my $cb = sub { |
|
|
205 | # cancel the old timer while creating a new one |
|
|
206 | $w = AnyEvent->timer (after => 1, cb => $cb); |
218 | my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub { |
|
|
219 | warn "timeout\n"; |
207 | }; |
220 | }; |
208 | |
|
|
209 | # start the "loop" by creating the first watcher |
|
|
210 | $w = AnyEvent->timer (after => 0.5, cb => $cb); |
|
|
211 | |
221 | |
212 | =head3 TIMING ISSUES |
222 | =head3 TIMING ISSUES |
213 | |
223 | |
214 | There are two ways to handle timers: based on real time (relative, "fire |
224 | There are two ways to handle timers: based on real time (relative, "fire |
215 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
225 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
… | |
… | |
226 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
236 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
227 | timers. |
237 | timers. |
228 | |
238 | |
229 | AnyEvent always prefers relative timers, if available, matching the |
239 | AnyEvent always prefers relative timers, if available, matching the |
230 | AnyEvent API. |
240 | AnyEvent API. |
|
|
241 | |
|
|
242 | AnyEvent has two additional methods that return the "current time": |
|
|
243 | |
|
|
244 | =over 4 |
|
|
245 | |
|
|
246 | =item AnyEvent->time |
|
|
247 | |
|
|
248 | This returns the "current wallclock time" as a fractional number of |
|
|
249 | seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time> |
|
|
250 | return, and the result is guaranteed to be compatible with those). |
|
|
251 | |
|
|
252 | It progresses independently of any event loop processing, i.e. each call |
|
|
253 | will check the system clock, which usually gets updated frequently. |
|
|
254 | |
|
|
255 | =item AnyEvent->now |
|
|
256 | |
|
|
257 | This also returns the "current wallclock time", but unlike C<time>, above, |
|
|
258 | this value might change only once per event loop iteration, depending on |
|
|
259 | the event loop (most return the same time as C<time>, above). This is the |
|
|
260 | time that AnyEvent's timers get scheduled against. |
|
|
261 | |
|
|
262 | I<In almost all cases (in all cases if you don't care), this is the |
|
|
263 | function to call when you want to know the current time.> |
|
|
264 | |
|
|
265 | This function is also often faster then C<< AnyEvent->time >>, and |
|
|
266 | thus the preferred method if you want some timestamp (for example, |
|
|
267 | L<AnyEvent::Handle> uses this to update it's activity timeouts). |
|
|
268 | |
|
|
269 | The rest of this section is only of relevance if you try to be very exact |
|
|
270 | with your timing, you can skip it without bad conscience. |
|
|
271 | |
|
|
272 | For a practical example of when these times differ, consider L<Event::Lib> |
|
|
273 | and L<EV> and the following set-up: |
|
|
274 | |
|
|
275 | The event loop is running and has just invoked one of your callback at |
|
|
276 | time=500 (assume no other callbacks delay processing). In your callback, |
|
|
277 | you wait a second by executing C<sleep 1> (blocking the process for a |
|
|
278 | second) and then (at time=501) you create a relative timer that fires |
|
|
279 | after three seconds. |
|
|
280 | |
|
|
281 | With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will |
|
|
282 | both return C<501>, because that is the current time, and the timer will |
|
|
283 | be scheduled to fire at time=504 (C<501> + C<3>). |
|
|
284 | |
|
|
285 | With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current |
|
|
286 | time), but C<< AnyEvent->now >> returns C<500>, as that is the time the |
|
|
287 | last event processing phase started. With L<EV>, your timer gets scheduled |
|
|
288 | to run at time=503 (C<500> + C<3>). |
|
|
289 | |
|
|
290 | In one sense, L<Event::Lib> is more exact, as it uses the current time |
|
|
291 | regardless of any delays introduced by event processing. However, most |
|
|
292 | callbacks do not expect large delays in processing, so this causes a |
|
|
293 | higher drift (and a lot more system calls to get the current time). |
|
|
294 | |
|
|
295 | In another sense, L<EV> is more exact, as your timer will be scheduled at |
|
|
296 | the same time, regardless of how long event processing actually took. |
|
|
297 | |
|
|
298 | In either case, if you care (and in most cases, you don't), then you |
|
|
299 | can get whatever behaviour you want with any event loop, by taking the |
|
|
300 | difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into |
|
|
301 | account. |
|
|
302 | |
|
|
303 | =back |
231 | |
304 | |
232 | =head2 SIGNAL WATCHERS |
305 | =head2 SIGNAL WATCHERS |
233 | |
306 | |
234 | You can watch for signals using a signal watcher, C<signal> is the signal |
307 | 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 |
308 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
… | |
… | |
277 | AnyEvent program, you I<have> to create at least one watcher before you |
350 | 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>). |
351 | C<fork> the child (alternatively, you can call C<AnyEvent::detect>). |
279 | |
352 | |
280 | Example: fork a process and wait for it |
353 | Example: fork a process and wait for it |
281 | |
354 | |
282 | my $done = AnyEvent->condvar; |
355 | my $done = AnyEvent->condvar; |
283 | |
356 | |
284 | my $pid = fork or exit 5; |
357 | my $pid = fork or exit 5; |
285 | |
358 | |
286 | my $w = AnyEvent->child ( |
359 | my $w = AnyEvent->child ( |
287 | pid => $pid, |
360 | pid => $pid, |
288 | cb => sub { |
361 | cb => sub { |
289 | my ($pid, $status) = @_; |
362 | my ($pid, $status) = @_; |
290 | warn "pid $pid exited with status $status"; |
363 | warn "pid $pid exited with status $status"; |
291 | $done->send; |
364 | $done->send; |
292 | }, |
365 | }, |
293 | ); |
366 | ); |
294 | |
367 | |
295 | # do something else, then wait for process exit |
368 | # do something else, then wait for process exit |
296 | $done->recv; |
369 | $done->recv; |
297 | |
370 | |
298 | =head2 CONDITION VARIABLES |
371 | =head2 CONDITION VARIABLES |
299 | |
372 | |
300 | If you are familiar with some event loops you will know that all of them |
373 | 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 |
374 | require you to run some blocking "loop", "run" or similar function that |
… | |
… | |
522 | |
595 | |
523 | This is a mutator function that returns the callback set and optionally |
596 | This is a mutator function that returns the callback set and optionally |
524 | replaces it before doing so. |
597 | replaces it before doing so. |
525 | |
598 | |
526 | The callback will be called when the condition becomes "true", i.e. when |
599 | The callback will be called when the condition becomes "true", i.e. when |
527 | C<send> or C<croak> are called. Calling C<recv> inside the callback |
600 | C<send> or C<croak> are called, with the only argument being the condition |
528 | or at any later time is guaranteed not to block. |
601 | variable itself. Calling C<recv> inside the callback or at any later time |
|
|
602 | is guaranteed not to block. |
529 | |
603 | |
530 | =back |
604 | =back |
531 | |
605 | |
532 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
606 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
533 | |
607 | |
… | |
… | |
662 | =item L<AnyEvent::Util> |
736 | =item L<AnyEvent::Util> |
663 | |
737 | |
664 | Contains various utility functions that replace often-used but blocking |
738 | Contains various utility functions that replace often-used but blocking |
665 | functions such as C<inet_aton> by event-/callback-based versions. |
739 | functions such as C<inet_aton> by event-/callback-based versions. |
666 | |
740 | |
667 | =item L<AnyEvent::Handle> |
|
|
668 | |
|
|
669 | Provide read and write buffers and manages watchers for reads and writes. |
|
|
670 | |
|
|
671 | =item L<AnyEvent::Socket> |
741 | =item L<AnyEvent::Socket> |
672 | |
742 | |
673 | Provides various utility functions for (internet protocol) sockets, |
743 | Provides various utility functions for (internet protocol) sockets, |
674 | addresses and name resolution. Also functions to create non-blocking tcp |
744 | addresses and name resolution. Also functions to create non-blocking tcp |
675 | connections or tcp servers, with IPv6 and SRV record support and more. |
745 | connections or tcp servers, with IPv6 and SRV record support and more. |
676 | |
746 | |
|
|
747 | =item L<AnyEvent::Handle> |
|
|
748 | |
|
|
749 | Provide read and write buffers, manages watchers for reads and writes, |
|
|
750 | supports raw and formatted I/O, I/O queued and fully transparent and |
|
|
751 | non-blocking SSL/TLS. |
|
|
752 | |
677 | =item L<AnyEvent::DNS> |
753 | =item L<AnyEvent::DNS> |
678 | |
754 | |
679 | Provides rich asynchronous DNS resolver capabilities. |
755 | Provides rich asynchronous DNS resolver capabilities. |
680 | |
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 | |
681 | =item L<AnyEvent::HTTPD> |
762 | =item L<AnyEvent::HTTPD> |
682 | |
763 | |
683 | Provides a simple web application server framework. |
764 | Provides a simple web application server framework. |
684 | |
765 | |
685 | =item L<AnyEvent::FastPing> |
766 | =item L<AnyEvent::FastPing> |
686 | |
767 | |
687 | The fastest ping in the west. |
768 | The fastest ping in the west. |
|
|
769 | |
|
|
770 | =item L<AnyEvent::DBI> |
|
|
771 | |
|
|
772 | Executes L<DBI> requests asynchronously in a proxy process. |
|
|
773 | |
|
|
774 | =item L<AnyEvent::AIO> |
|
|
775 | |
|
|
776 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
777 | programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent |
|
|
778 | together. |
|
|
779 | |
|
|
780 | =item L<AnyEvent::BDB> |
|
|
781 | |
|
|
782 | Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses |
|
|
783 | L<BDB> and AnyEvent together. |
|
|
784 | |
|
|
785 | =item L<AnyEvent::GPSD> |
|
|
786 | |
|
|
787 | A non-blocking interface to gpsd, a daemon delivering GPS information. |
|
|
788 | |
|
|
789 | =item L<AnyEvent::IGS> |
|
|
790 | |
|
|
791 | A non-blocking interface to the Internet Go Server protocol (used by |
|
|
792 | L<App::IGS>). |
688 | |
793 | |
689 | =item L<Net::IRC3> |
794 | =item L<Net::IRC3> |
690 | |
795 | |
691 | AnyEvent based IRC client module family. |
796 | AnyEvent based IRC client module family. |
692 | |
797 | |
… | |
… | |
705 | |
810 | |
706 | =item L<Coro> |
811 | =item L<Coro> |
707 | |
812 | |
708 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
813 | Has special support for AnyEvent via L<Coro::AnyEvent>. |
709 | |
814 | |
710 | =item L<AnyEvent::AIO>, L<IO::AIO> |
|
|
711 | |
|
|
712 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
713 | programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent |
|
|
714 | together. |
|
|
715 | |
|
|
716 | =item L<AnyEvent::BDB>, L<BDB> |
|
|
717 | |
|
|
718 | Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses |
|
|
719 | IO::AIO and AnyEvent together. |
|
|
720 | |
|
|
721 | =item L<IO::Lambda> |
815 | =item L<IO::Lambda> |
722 | |
816 | |
723 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
817 | The lambda approach to I/O - don't ask, look there. Can use AnyEvent. |
724 | |
818 | |
725 | =back |
819 | =back |
… | |
… | |
731 | no warnings; |
825 | no warnings; |
732 | use strict; |
826 | use strict; |
733 | |
827 | |
734 | use Carp; |
828 | use Carp; |
735 | |
829 | |
736 | our $VERSION = '4.05'; |
830 | our $VERSION = 4.2; |
737 | our $MODEL; |
831 | our $MODEL; |
738 | |
832 | |
739 | our $AUTOLOAD; |
833 | our $AUTOLOAD; |
740 | our @ISA; |
834 | our @ISA; |
741 | |
835 | |
… | |
… | |
773 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
867 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
774 | [Wx:: => AnyEvent::Impl::POE::], |
868 | [Wx:: => AnyEvent::Impl::POE::], |
775 | [Prima:: => AnyEvent::Impl::POE::], |
869 | [Prima:: => AnyEvent::Impl::POE::], |
776 | ); |
870 | ); |
777 | |
871 | |
778 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
872 | our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); |
779 | |
873 | |
780 | our @post_detect; |
874 | our @post_detect; |
781 | |
875 | |
782 | sub post_detect(&) { |
876 | sub post_detect(&) { |
783 | my ($cb) = @_; |
877 | my ($cb) = @_; |
… | |
… | |
867 | $class->$func (@_); |
961 | $class->$func (@_); |
868 | } |
962 | } |
869 | |
963 | |
870 | package AnyEvent::Base; |
964 | package AnyEvent::Base; |
871 | |
965 | |
|
|
966 | # default implementation for now and time |
|
|
967 | |
|
|
968 | use Time::HiRes (); |
|
|
969 | |
|
|
970 | sub time { Time::HiRes::time } |
|
|
971 | sub now { Time::HiRes::time } |
|
|
972 | |
872 | # default implementation for ->condvar |
973 | # default implementation for ->condvar |
873 | |
974 | |
874 | sub condvar { |
975 | sub condvar { |
875 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
976 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
876 | } |
977 | } |
… | |
… | |
896 | sub AnyEvent::Base::Signal::DESTROY { |
997 | sub AnyEvent::Base::Signal::DESTROY { |
897 | my ($signal, $cb) = @{$_[0]}; |
998 | my ($signal, $cb) = @{$_[0]}; |
898 | |
999 | |
899 | delete $SIG_CB{$signal}{$cb}; |
1000 | delete $SIG_CB{$signal}{$cb}; |
900 | |
1001 | |
901 | $SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} }; |
1002 | delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} }; |
902 | } |
1003 | } |
903 | |
1004 | |
904 | # default implementation for ->child |
1005 | # default implementation for ->child |
905 | |
1006 | |
906 | our %PID_CB; |
1007 | our %PID_CB; |
… | |
… | |
1090 | This functionality might change in future versions. |
1191 | This functionality might change in future versions. |
1091 | |
1192 | |
1092 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
1193 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
1093 | could start your program like this: |
1194 | could start your program like this: |
1094 | |
1195 | |
1095 | PERL_ANYEVENT_MODEL=Perl perl ... |
1196 | PERL_ANYEVENT_MODEL=Perl perl ... |
1096 | |
1197 | |
1097 | =item C<PERL_ANYEVENT_PROTOCOLS> |
1198 | =item C<PERL_ANYEVENT_PROTOCOLS> |
1098 | |
1199 | |
1099 | Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences |
1200 | Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences |
1100 | for IPv4 or IPv6. The default is unspecified (and might change, or be the result |
1201 | for IPv4 or IPv6. The default is unspecified (and might change, or be the result |
… | |
… | |
1122 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1223 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1123 | default. |
1224 | default. |
1124 | |
1225 | |
1125 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1226 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1126 | EDNS0 in its DNS requests. |
1227 | EDNS0 in its DNS requests. |
|
|
1228 | |
|
|
1229 | =item C<PERL_ANYEVENT_MAX_FORKS> |
|
|
1230 | |
|
|
1231 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
|
|
1232 | will create in parallel. |
1127 | |
1233 | |
1128 | =back |
1234 | =back |
1129 | |
1235 | |
1130 | =head1 EXAMPLE PROGRAM |
1236 | =head1 EXAMPLE PROGRAM |
1131 | |
1237 | |
… | |
… | |
1570 | specified in the variable. |
1676 | specified in the variable. |
1571 | |
1677 | |
1572 | You can make AnyEvent completely ignore this variable by deleting it |
1678 | You can make AnyEvent completely ignore this variable by deleting it |
1573 | before the first watcher gets created, e.g. with a C<BEGIN> block: |
1679 | before the first watcher gets created, e.g. with a C<BEGIN> block: |
1574 | |
1680 | |
1575 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1681 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
1576 | |
1682 | |
1577 | use AnyEvent; |
1683 | use AnyEvent; |
1578 | |
1684 | |
1579 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
1685 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
1580 | be used to probe what backend is used and gain other information (which is |
1686 | be used to probe what backend is used and gain other information (which is |
1581 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
1687 | probably even less useful to an attacker than PERL_ANYEVENT_MODEL). |
|
|
1688 | |
|
|
1689 | |
|
|
1690 | =head1 BUGS |
|
|
1691 | |
|
|
1692 | Perl 5.8 has numerous memleaks that sometimes hit this module and are hard |
|
|
1693 | to work around. If you suffer from memleaks, first upgrade to Perl 5.10 |
|
|
1694 | and check wether the leaks still show up. (Perl 5.10.0 has other annoying |
|
|
1695 | mamleaks, such as leaking on C<map> and C<grep> but it is usually not as |
|
|
1696 | pronounced). |
1582 | |
1697 | |
1583 | |
1698 | |
1584 | =head1 SEE ALSO |
1699 | =head1 SEE ALSO |
1585 | |
1700 | |
1586 | Utility functions: L<AnyEvent::Util>. |
1701 | Utility functions: L<AnyEvent::Util>. |
… | |
… | |
1603 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
1718 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>. |
1604 | |
1719 | |
1605 | |
1720 | |
1606 | =head1 AUTHOR |
1721 | =head1 AUTHOR |
1607 | |
1722 | |
1608 | Marc Lehmann <schmorp@schmorp.de> |
1723 | Marc Lehmann <schmorp@schmorp.de> |
1609 | http://home.schmorp.de/ |
1724 | http://home.schmorp.de/ |
1610 | |
1725 | |
1611 | =cut |
1726 | =cut |
1612 | |
1727 | |
1613 | 1 |
1728 | 1 |
1614 | |
1729 | |