1 | NAME |
1 | NAME |
2 | AnyEvent - provide framework for multiple event loops |
2 | AnyEvent - provide framework for multiple event loops |
3 | |
3 | |
4 | EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl - various supported |
4 | EV, Event, Glib, Tk, Perl, Event::Lib, Qt and POE are various supported |
5 | event loops |
5 | event loops. |
6 | |
6 | |
7 | SYNOPSIS |
7 | SYNOPSIS |
8 | use AnyEvent; |
8 | use AnyEvent; |
9 | |
9 | |
|
|
10 | # file descriptor readable |
10 | my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { |
11 | my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... }); |
|
|
12 | |
|
|
13 | # one-shot or repeating timers |
|
|
14 | my $w = AnyEvent->timer (after => $seconds, cb => sub { ... }); |
|
|
15 | my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ... |
|
|
16 | |
|
|
17 | print AnyEvent->now; # prints current event loop time |
|
|
18 | print AnyEvent->time; # think Time::HiRes::time or simply CORE::time. |
|
|
19 | |
|
|
20 | # POSIX signal |
|
|
21 | my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... }); |
|
|
22 | |
|
|
23 | # child process exit |
|
|
24 | my $w = AnyEvent->child (pid => $pid, cb => sub { |
|
|
25 | my ($pid, $status) = @_; |
11 | ... |
26 | ... |
12 | }); |
27 | }); |
13 | |
28 | |
14 | my $w = AnyEvent->timer (after => $seconds, cb => sub { |
29 | # called when event loop idle (if applicable) |
15 | ... |
30 | my $w = AnyEvent->idle (cb => sub { ... }); |
16 | }); |
|
|
17 | |
31 | |
18 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
32 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
|
|
33 | $w->send; # wake up current and all future recv's |
19 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
34 | $w->recv; # enters "main loop" till $condvar gets ->send |
20 | $w->broadcast; # wake up current and all future wait's |
35 | # use a condvar in callback mode: |
|
|
36 | $w->cb (sub { $_[0]->recv }); |
|
|
37 | |
|
|
38 | INTRODUCTION/TUTORIAL |
|
|
39 | This manpage is mainly a reference manual. If you are interested in a |
|
|
40 | tutorial or some gentle introduction, have a look at the AnyEvent::Intro |
|
|
41 | manpage. |
21 | |
42 | |
22 | WHY YOU SHOULD USE THIS MODULE (OR NOT) |
43 | WHY YOU SHOULD USE THIS MODULE (OR NOT) |
23 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
44 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
24 | nowadays. So what is different about AnyEvent? |
45 | nowadays. So what is different about AnyEvent? |
25 | |
46 | |
26 | Executive Summary: AnyEvent is *compatible*, AnyEvent is *free of |
47 | Executive Summary: AnyEvent is *compatible*, AnyEvent is *free of |
27 | policy* and AnyEvent is *small and efficient*. |
48 | policy* and AnyEvent is *small and efficient*. |
28 | |
49 | |
29 | First and foremost, *AnyEvent is not an event model* itself, it only |
50 | First and foremost, *AnyEvent is not an event model* itself, it only |
30 | interfaces to whatever event model the main program happens to use in a |
51 | interfaces to whatever event model the main program happens to use, in a |
31 | pragmatic way. For event models and certain classes of immortals alike, |
52 | pragmatic way. For event models and certain classes of immortals alike, |
32 | the statement "there can only be one" is a bitter reality: In general, |
53 | the statement "there can only be one" is a bitter reality: In general, |
33 | only one event loop can be active at the same time in a process. |
54 | only one event loop can be active at the same time in a process. |
34 | AnyEvent helps hiding the differences between those event loops. |
55 | AnyEvent cannot change this, but it can hide the differences between |
|
|
56 | those event loops. |
35 | |
57 | |
36 | The goal of AnyEvent is to offer module authors the ability to do event |
58 | The goal of AnyEvent is to offer module authors the ability to do event |
37 | programming (waiting for I/O or timer events) without subscribing to a |
59 | programming (waiting for I/O or timer events) without subscribing to a |
38 | religion, a way of living, and most importantly: without forcing your |
60 | religion, a way of living, and most importantly: without forcing your |
39 | module users into the same thing by forcing them to use the same event |
61 | module users into the same thing by forcing them to use the same event |
40 | model you use. |
62 | model you use. |
41 | |
63 | |
42 | For modules like POE or IO::Async (which is a total misnomer as it is |
64 | For modules like POE or IO::Async (which is a total misnomer as it is |
43 | actually doing all I/O *synchronously*...), using them in your module is |
65 | actually doing all I/O *synchronously*...), using them in your module is |
44 | like joining a cult: After you joined, you are dependent on them and you |
66 | like joining a cult: After you joined, you are dependent on them and you |
45 | cannot use anything else, as it is simply incompatible to everything |
67 | cannot use anything else, as they are simply incompatible to everything |
46 | that isn't itself. What's worse, all the potential users of your module |
68 | that isn't them. What's worse, all the potential users of your module |
47 | are *also* forced to use the same event loop you use. |
69 | are *also* forced to use the same event loop you use. |
48 | |
70 | |
49 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
71 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
50 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
72 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
51 | with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if your |
73 | with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if your |
52 | module uses one of those, every user of your module has to use it, too. |
74 | module uses one of those, every user of your module has to use it, too. |
53 | But if your module uses AnyEvent, it works transparently with all event |
75 | But if your module uses AnyEvent, it works transparently with all event |
54 | models it supports (including stuff like POE and IO::Async, as long as |
76 | models it supports (including stuff like IO::Async, as long as those use |
55 | those use one of the supported event loops. It is trivial to add new |
77 | one of the supported event loops. It is trivial to add new event loops |
56 | event loops to AnyEvent, too, so it is future-proof). |
78 | to AnyEvent, too, so it is future-proof). |
57 | |
79 | |
58 | In addition to being free of having to use *the one and only true event |
80 | In addition to being free of having to use *the one and only true event |
59 | model*, AnyEvent also is free of bloat and policy: with POE or similar |
81 | model*, AnyEvent also is free of bloat and policy: with POE or similar |
60 | modules, you get an enourmous amount of code and strict rules you have |
82 | modules, you get an enormous amount of code and strict rules you have to |
61 | to follow. AnyEvent, on the other hand, is lean and up to the point, by |
83 | follow. AnyEvent, on the other hand, is lean and up to the point, by |
62 | only offering the functionality that is necessary, in as thin as a |
84 | only offering the functionality that is necessary, in as thin as a |
63 | wrapper as technically possible. |
85 | wrapper as technically possible. |
64 | |
86 | |
|
|
87 | Of course, AnyEvent comes with a big (and fully optional!) toolbox of |
|
|
88 | useful functionality, such as an asynchronous DNS resolver, 100% |
|
|
89 | non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms |
|
|
90 | such as Windows) and lots of real-world knowledge and workarounds for |
|
|
91 | platform bugs and differences. |
|
|
92 | |
65 | Of course, if you want lots of policy (this can arguably be somewhat |
93 | Now, if you *do want* lots of policy (this can arguably be somewhat |
66 | useful) and you want to force your users to use the one and only event |
94 | useful) and you want to force your users to use the one and only event |
67 | model, you should *not* use this module. |
95 | model, you should *not* use this module. |
68 | |
96 | |
69 | DESCRIPTION |
97 | DESCRIPTION |
70 | AnyEvent provides an identical interface to multiple event loops. This |
98 | AnyEvent provides an identical interface to multiple event loops. This |
… | |
… | |
75 | The interface itself is vaguely similar, but not identical to the Event |
103 | The interface itself is vaguely similar, but not identical to the Event |
76 | module. |
104 | module. |
77 | |
105 | |
78 | During the first call of any watcher-creation method, the module tries |
106 | During the first call of any watcher-creation method, the module tries |
79 | to detect the currently loaded event loop by probing whether one of the |
107 | to detect the currently loaded event loop by probing whether one of the |
80 | following modules is already loaded: Coro::EV, Coro::Event, EV, Event, |
108 | following modules is already loaded: EV, Event, Glib, |
81 | Glib, Tk. The first one found is used. If none are found, the module |
109 | AnyEvent::Impl::Perl, Tk, Event::Lib, Qt, POE. The first one found is |
82 | tries to load these modules in the stated order. The first one that can |
110 | used. If none are found, the module tries to load these modules |
|
|
111 | (excluding Tk, Event::Lib, Qt and POE as the pure perl adaptor should |
|
|
112 | always succeed) in the order given. The first one that can be |
83 | be successfully loaded will be used. If, after this, still none could be |
113 | successfully loaded will be used. If, after this, still none could be |
84 | found, AnyEvent will fall back to a pure-perl event loop, which is not |
114 | found, AnyEvent will fall back to a pure-perl event loop, which is not |
85 | very efficient, but should work everywhere. |
115 | very efficient, but should work everywhere. |
86 | |
116 | |
87 | Because AnyEvent first checks for modules that are already loaded, |
117 | Because AnyEvent first checks for modules that are already loaded, |
88 | loading an event model explicitly before first using AnyEvent will |
118 | loading an event model explicitly before first using AnyEvent will |
… | |
… | |
97 | starts using it, all bets are off. Maybe you should tell their authors |
127 | starts using it, all bets are off. Maybe you should tell their authors |
98 | to use AnyEvent so their modules work together with others seamlessly... |
128 | to use AnyEvent so their modules work together with others seamlessly... |
99 | |
129 | |
100 | The pure-perl implementation of AnyEvent is called |
130 | The pure-perl implementation of AnyEvent is called |
101 | "AnyEvent::Impl::Perl". Like other event modules you can load it |
131 | "AnyEvent::Impl::Perl". Like other event modules you can load it |
102 | explicitly. |
132 | explicitly and enjoy the high availability of that event loop :) |
103 | |
133 | |
104 | WATCHERS |
134 | WATCHERS |
105 | AnyEvent has the central concept of a *watcher*, which is an object that |
135 | AnyEvent has the central concept of a *watcher*, which is an object that |
106 | stores relevant data for each kind of event you are waiting for, such as |
136 | stores relevant data for each kind of event you are waiting for, such as |
107 | the callback to call, the filehandle to watch, etc. |
137 | the callback to call, the file handle to watch, etc. |
108 | |
138 | |
109 | These watchers are normal Perl objects with normal Perl lifetime. After |
139 | These watchers are normal Perl objects with normal Perl lifetime. After |
110 | creating a watcher it will immediately "watch" for events and invoke the |
140 | creating a watcher it will immediately "watch" for events and invoke the |
111 | callback when the event occurs (of course, only when the event model is |
141 | callback when the event occurs (of course, only when the event model is |
112 | in control). |
142 | in control). |
113 | |
143 | |
|
|
144 | Note that callbacks must not permanently change global variables |
|
|
145 | potentially in use by the event loop (such as $_ or $[) and that |
|
|
146 | callbacks must not "die". The former is good programming practise in |
|
|
147 | Perl and the latter stems from the fact that exception handling differs |
|
|
148 | widely between event loops. |
|
|
149 | |
114 | To disable the watcher you have to destroy it (e.g. by setting the |
150 | To disable the watcher you have to destroy it (e.g. by setting the |
115 | variable you store it in to "undef" or otherwise deleting all references |
151 | variable you store it in to "undef" or otherwise deleting all references |
116 | to it). |
152 | to it). |
117 | |
153 | |
118 | All watchers are created by calling a method on the "AnyEvent" class. |
154 | All watchers are created by calling a method on the "AnyEvent" class. |
… | |
… | |
120 | Many watchers either are used with "recursion" (repeating timers for |
156 | Many watchers either are used with "recursion" (repeating timers for |
121 | example), or need to refer to their watcher object in other ways. |
157 | example), or need to refer to their watcher object in other ways. |
122 | |
158 | |
123 | An any way to achieve that is this pattern: |
159 | An any way to achieve that is this pattern: |
124 | |
160 | |
125 | my $w; $w = AnyEvent->type (arg => value ..., cb => sub { |
161 | my $w; $w = AnyEvent->type (arg => value ..., cb => sub { |
126 | # you can use $w here, for example to undef it |
162 | # you can use $w here, for example to undef it |
127 | undef $w; |
163 | undef $w; |
128 | }); |
164 | }); |
129 | |
165 | |
130 | Note that "my $w; $w =" combination. This is necessary because in Perl, |
166 | Note that "my $w; $w =" combination. This is necessary because in Perl, |
131 | my variables are only visible after the statement in which they are |
167 | my variables are only visible after the statement in which they are |
132 | declared. |
168 | declared. |
133 | |
169 | |
134 | IO WATCHERS |
170 | I/O WATCHERS |
135 | You can create an I/O watcher by calling the "AnyEvent->io" method with |
171 | You can create an I/O watcher by calling the "AnyEvent->io" method with |
136 | the following mandatory key-value pairs as arguments: |
172 | the following mandatory key-value pairs as arguments: |
137 | |
173 | |
138 | "fh" the Perl *file handle* (*not* file descriptor) to watch for events. |
174 | "fh" is the Perl *file handle* (or a naked file descriptor) to watch for |
|
|
175 | events (AnyEvent might or might not keep a reference to this file |
|
|
176 | handle). Note that only file handles pointing to things for which |
|
|
177 | non-blocking operation makes sense are allowed. This includes sockets, |
|
|
178 | most character devices, pipes, fifos and so on, but not for example |
|
|
179 | files or block devices. |
|
|
180 | |
139 | "poll" must be a string that is either "r" or "w", which creates a |
181 | "poll" must be a string that is either "r" or "w", which creates a |
140 | watcher waiting for "r"eadable or "w"ritable events, respectively. "cb" |
182 | watcher waiting for "r"eadable or "w"ritable events, respectively. |
|
|
183 | |
141 | is the callback to invoke each time the file handle becomes ready. |
184 | "cb" is the callback to invoke each time the file handle becomes ready. |
142 | |
185 | |
143 | File handles will be kept alive, so as long as the watcher exists, the |
186 | Although the callback might get passed parameters, their value and |
144 | file handle exists, too. |
187 | presence is undefined and you cannot rely on them. Portable AnyEvent |
|
|
188 | callbacks cannot use arguments passed to I/O watcher callbacks. |
145 | |
189 | |
|
|
190 | The I/O watcher might use the underlying file descriptor or a copy of |
146 | It is not allowed to close a file handle as long as any watcher is |
191 | it. You must not close a file handle as long as any watcher is active on |
147 | active on the underlying file descriptor. |
192 | the underlying file descriptor. |
148 | |
193 | |
149 | Some event loops issue spurious readyness notifications, so you should |
194 | Some event loops issue spurious readyness notifications, so you should |
150 | always use non-blocking calls when reading/writing from/to your file |
195 | always use non-blocking calls when reading/writing from/to your file |
151 | handles. |
196 | handles. |
152 | |
197 | |
153 | Example: |
|
|
154 | |
|
|
155 | # wait for readability of STDIN, then read a line and disable the watcher |
198 | Example: wait for readability of STDIN, then read a line and disable the |
|
|
199 | watcher. |
|
|
200 | |
156 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
201 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
157 | chomp (my $input = <STDIN>); |
202 | chomp (my $input = <STDIN>); |
158 | warn "read: $input\n"; |
203 | warn "read: $input\n"; |
159 | undef $w; |
204 | undef $w; |
160 | }); |
205 | }); |
… | |
… | |
162 | TIME WATCHERS |
207 | TIME WATCHERS |
163 | You can create a time watcher by calling the "AnyEvent->timer" method |
208 | You can create a time watcher by calling the "AnyEvent->timer" method |
164 | with the following mandatory arguments: |
209 | with the following mandatory arguments: |
165 | |
210 | |
166 | "after" specifies after how many seconds (fractional values are |
211 | "after" specifies after how many seconds (fractional values are |
167 | supported) should the timer activate. "cb" the callback to invoke in |
212 | supported) the callback should be invoked. "cb" is the callback to |
168 | that case. |
213 | invoke in that case. |
169 | |
214 | |
170 | The timer callback will be invoked at most once: if you want a repeating |
215 | Although the callback might get passed parameters, their value and |
171 | timer you have to create a new watcher (this is a limitation by both Tk |
216 | presence is undefined and you cannot rely on them. Portable AnyEvent |
172 | and Glib). |
217 | callbacks cannot use arguments passed to time watcher callbacks. |
173 | |
218 | |
174 | Example: |
219 | The callback will normally be invoked once only. If you specify another |
|
|
220 | parameter, "interval", as a strictly positive number (> 0), then the |
|
|
221 | callback will be invoked regularly at that interval (in fractional |
|
|
222 | seconds) after the first invocation. If "interval" is specified with a |
|
|
223 | false value, then it is treated as if it were missing. |
175 | |
224 | |
|
|
225 | The callback will be rescheduled before invoking the callback, but no |
|
|
226 | attempt is done to avoid timer drift in most backends, so the interval |
|
|
227 | is only approximate. |
|
|
228 | |
176 | # fire an event after 7.7 seconds |
229 | Example: fire an event after 7.7 seconds. |
|
|
230 | |
177 | my $w = AnyEvent->timer (after => 7.7, cb => sub { |
231 | my $w = AnyEvent->timer (after => 7.7, cb => sub { |
178 | warn "timeout\n"; |
232 | warn "timeout\n"; |
179 | }); |
233 | }); |
180 | |
234 | |
181 | # to cancel the timer: |
235 | # to cancel the timer: |
182 | undef $w; |
236 | undef $w; |
183 | |
237 | |
184 | Example 2: |
|
|
185 | |
|
|
186 | # fire an event after 0.5 seconds, then roughly every second |
238 | Example 2: fire an event after 0.5 seconds, then roughly every second. |
187 | my $w; |
|
|
188 | |
239 | |
189 | my $cb = sub { |
|
|
190 | # cancel the old timer while creating a new one |
|
|
191 | $w = AnyEvent->timer (after => 1, cb => $cb); |
240 | my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub { |
|
|
241 | warn "timeout\n"; |
192 | }; |
242 | }; |
193 | |
|
|
194 | # start the "loop" by creating the first watcher |
|
|
195 | $w = AnyEvent->timer (after => 0.5, cb => $cb); |
|
|
196 | |
243 | |
197 | TIMING ISSUES |
244 | TIMING ISSUES |
198 | There are two ways to handle timers: based on real time (relative, "fire |
245 | There are two ways to handle timers: based on real time (relative, "fire |
199 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
246 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
200 | o'clock"). |
247 | o'clock"). |
201 | |
248 | |
202 | While most event loops expect timers to specified in a relative way, |
249 | While most event loops expect timers to specified in a relative way, |
203 | they use absolute time internally. This makes a difference when your |
250 | they use absolute time internally. This makes a difference when your |
204 | clock "jumps", for example, when ntp decides to set your clock backwards |
251 | clock "jumps", for example, when ntp decides to set your clock backwards |
205 | from the wrong 2014-01-01 to 2008-01-01, a watcher that you created to |
252 | from the wrong date of 2014-01-01 to 2008-01-01, a watcher that is |
206 | fire "after" a second might actually take six years to finally fire. |
253 | supposed to fire "after" a second might actually take six years to |
|
|
254 | finally fire. |
207 | |
255 | |
208 | AnyEvent cannot compensate for this. The only event loop that is |
256 | AnyEvent cannot compensate for this. The only event loop that is |
209 | conscious about these issues is EV, which offers both relative |
257 | conscious about these issues is EV, which offers both relative |
210 | (ev_timer) and absolute (ev_periodic) timers. |
258 | (ev_timer, based on true relative time) and absolute (ev_periodic, based |
|
|
259 | on wallclock time) timers. |
211 | |
260 | |
212 | AnyEvent always prefers relative timers, if available, matching the |
261 | AnyEvent always prefers relative timers, if available, matching the |
213 | AnyEvent API. |
262 | AnyEvent API. |
214 | |
263 | |
|
|
264 | AnyEvent has two additional methods that return the "current time": |
|
|
265 | |
|
|
266 | AnyEvent->time |
|
|
267 | This returns the "current wallclock time" as a fractional number of |
|
|
268 | seconds since the Epoch (the same thing as "time" or |
|
|
269 | "Time::HiRes::time" return, and the result is guaranteed to be |
|
|
270 | compatible with those). |
|
|
271 | |
|
|
272 | It progresses independently of any event loop processing, i.e. each |
|
|
273 | call will check the system clock, which usually gets updated |
|
|
274 | frequently. |
|
|
275 | |
|
|
276 | AnyEvent->now |
|
|
277 | This also returns the "current wallclock time", but unlike "time", |
|
|
278 | above, this value might change only once per event loop iteration, |
|
|
279 | depending on the event loop (most return the same time as "time", |
|
|
280 | above). This is the time that AnyEvent's timers get scheduled |
|
|
281 | against. |
|
|
282 | |
|
|
283 | *In almost all cases (in all cases if you don't care), this is the |
|
|
284 | function to call when you want to know the current time.* |
|
|
285 | |
|
|
286 | This function is also often faster then "AnyEvent->time", and thus |
|
|
287 | the preferred method if you want some timestamp (for example, |
|
|
288 | AnyEvent::Handle uses this to update it's activity timeouts). |
|
|
289 | |
|
|
290 | The rest of this section is only of relevance if you try to be very |
|
|
291 | exact with your timing, you can skip it without bad conscience. |
|
|
292 | |
|
|
293 | For a practical example of when these times differ, consider |
|
|
294 | Event::Lib and EV and the following set-up: |
|
|
295 | |
|
|
296 | The event loop is running and has just invoked one of your callback |
|
|
297 | at time=500 (assume no other callbacks delay processing). In your |
|
|
298 | callback, you wait a second by executing "sleep 1" (blocking the |
|
|
299 | process for a second) and then (at time=501) you create a relative |
|
|
300 | timer that fires after three seconds. |
|
|
301 | |
|
|
302 | With Event::Lib, "AnyEvent->time" and "AnyEvent->now" will both |
|
|
303 | return 501, because that is the current time, and the timer will be |
|
|
304 | scheduled to fire at time=504 (501 + 3). |
|
|
305 | |
|
|
306 | With EV, "AnyEvent->time" returns 501 (as that is the current time), |
|
|
307 | but "AnyEvent->now" returns 500, as that is the time the last event |
|
|
308 | processing phase started. With EV, your timer gets scheduled to run |
|
|
309 | at time=503 (500 + 3). |
|
|
310 | |
|
|
311 | In one sense, Event::Lib is more exact, as it uses the current time |
|
|
312 | regardless of any delays introduced by event processing. However, |
|
|
313 | most callbacks do not expect large delays in processing, so this |
|
|
314 | causes a higher drift (and a lot more system calls to get the |
|
|
315 | current time). |
|
|
316 | |
|
|
317 | In another sense, EV is more exact, as your timer will be scheduled |
|
|
318 | at the same time, regardless of how long event processing actually |
|
|
319 | took. |
|
|
320 | |
|
|
321 | In either case, if you care (and in most cases, you don't), then you |
|
|
322 | can get whatever behaviour you want with any event loop, by taking |
|
|
323 | the difference between "AnyEvent->time" and "AnyEvent->now" into |
|
|
324 | account. |
|
|
325 | |
|
|
326 | AnyEvent->now_update |
|
|
327 | Some event loops (such as EV or AnyEvent::Impl::Perl) cache the |
|
|
328 | current time for each loop iteration (see the discussion of |
|
|
329 | AnyEvent->now, above). |
|
|
330 | |
|
|
331 | When a callback runs for a long time (or when the process sleeps), |
|
|
332 | then this "current" time will differ substantially from the real |
|
|
333 | time, which might affect timers and time-outs. |
|
|
334 | |
|
|
335 | When this is the case, you can call this method, which will update |
|
|
336 | the event loop's idea of "current time". |
|
|
337 | |
|
|
338 | Note that updating the time *might* cause some events to be handled. |
|
|
339 | |
215 | SIGNAL WATCHERS |
340 | SIGNAL WATCHERS |
216 | You can watch for signals using a signal watcher, "signal" is the signal |
341 | You can watch for signals using a signal watcher, "signal" is the signal |
217 | *name* without any "SIG" prefix, "cb" is the Perl callback to be invoked |
342 | *name* in uppercase and without any "SIG" prefix, "cb" is the Perl |
218 | whenever a signal occurs. |
343 | callback to be invoked whenever a signal occurs. |
219 | |
344 | |
|
|
345 | Although the callback might get passed parameters, their value and |
|
|
346 | presence is undefined and you cannot rely on them. Portable AnyEvent |
|
|
347 | callbacks cannot use arguments passed to signal watcher callbacks. |
|
|
348 | |
220 | Multiple signals occurances can be clumped together into one callback |
349 | Multiple signal occurrences can be clumped together into one callback |
221 | invocation, and callback invocation will be synchronous. synchronous |
350 | invocation, and callback invocation will be synchronous. Synchronous |
222 | means that it might take a while until the signal gets handled by the |
351 | means that it might take a while until the signal gets handled by the |
223 | process, but it is guarenteed not to interrupt any other callbacks. |
352 | process, but it is guaranteed not to interrupt any other callbacks. |
224 | |
353 | |
225 | The main advantage of using these watchers is that you can share a |
354 | The main advantage of using these watchers is that you can share a |
226 | signal between multiple watchers. |
355 | signal between multiple watchers. |
227 | |
356 | |
228 | This watcher might use %SIG, so programs overwriting those signals |
357 | This watcher might use %SIG, so programs overwriting those signals |
… | |
… | |
234 | |
363 | |
235 | CHILD PROCESS WATCHERS |
364 | CHILD PROCESS WATCHERS |
236 | You can also watch on a child process exit and catch its exit status. |
365 | You can also watch on a child process exit and catch its exit status. |
237 | |
366 | |
238 | The child process is specified by the "pid" argument (if set to 0, it |
367 | The child process is specified by the "pid" argument (if set to 0, it |
239 | watches for any child process exit). The watcher will trigger as often |
368 | watches for any child process exit). The watcher will triggered only |
240 | as status change for the child are received. This works by installing a |
369 | when the child process has finished and an exit status is available, not |
241 | signal handler for "SIGCHLD". The callback will be called with the pid |
370 | on any trace events (stopped/continued). |
242 | and exit status (as returned by waitpid). |
|
|
243 | |
371 | |
244 | Example: wait for pid 1333 |
372 | The callback will be called with the pid and exit status (as returned by |
|
|
373 | waitpid), so unlike other watcher types, you *can* rely on child watcher |
|
|
374 | callback arguments. |
245 | |
375 | |
|
|
376 | This watcher type works by installing a signal handler for "SIGCHLD", |
|
|
377 | and since it cannot be shared, nothing else should use SIGCHLD or reap |
|
|
378 | random child processes (waiting for specific child processes, e.g. |
|
|
379 | inside "system", is just fine). |
|
|
380 | |
|
|
381 | There is a slight catch to child watchers, however: you usually start |
|
|
382 | them *after* the child process was created, and this means the process |
|
|
383 | could have exited already (and no SIGCHLD will be sent anymore). |
|
|
384 | |
|
|
385 | Not all event models handle this correctly (neither POE nor IO::Async |
|
|
386 | do, see their AnyEvent::Impl manpages for details), but even for event |
|
|
387 | models that *do* handle this correctly, they usually need to be loaded |
|
|
388 | before the process exits (i.e. before you fork in the first place). |
|
|
389 | AnyEvent's pure perl event loop handles all cases correctly regardless |
|
|
390 | of when you start the watcher. |
|
|
391 | |
|
|
392 | This means you cannot create a child watcher as the very first thing in |
|
|
393 | an AnyEvent program, you *have* to create at least one watcher before |
|
|
394 | you "fork" the child (alternatively, you can call "AnyEvent::detect"). |
|
|
395 | |
|
|
396 | Example: fork a process and wait for it |
|
|
397 | |
|
|
398 | my $done = AnyEvent->condvar; |
|
|
399 | |
|
|
400 | my $pid = fork or exit 5; |
|
|
401 | |
246 | my $w = AnyEvent->child ( |
402 | my $w = AnyEvent->child ( |
247 | pid => 1333, |
403 | pid => $pid, |
248 | cb => sub { |
404 | cb => sub { |
249 | my ($pid, $status) = @_; |
405 | my ($pid, $status) = @_; |
250 | warn "pid $pid exited with status $status"; |
406 | warn "pid $pid exited with status $status"; |
|
|
407 | $done->send; |
251 | }, |
408 | }, |
252 | ); |
409 | ); |
|
|
410 | |
|
|
411 | # do something else, then wait for process exit |
|
|
412 | $done->recv; |
|
|
413 | |
|
|
414 | IDLE WATCHERS |
|
|
415 | Sometimes there is a need to do something, but it is not so important to |
|
|
416 | do it instantly, but only when there is nothing better to do. This |
|
|
417 | "nothing better to do" is usually defined to be "no other events need |
|
|
418 | attention by the event loop". |
|
|
419 | |
|
|
420 | Idle watchers ideally get invoked when the event loop has nothing better |
|
|
421 | to do, just before it would block the process to wait for new events. |
|
|
422 | Instead of blocking, the idle watcher is invoked. |
|
|
423 | |
|
|
424 | Most event loops unfortunately do not really support idle watchers (only |
|
|
425 | EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent |
|
|
426 | will simply call the callback "from time to time". |
|
|
427 | |
|
|
428 | Example: read lines from STDIN, but only process them when the program |
|
|
429 | is otherwise idle: |
|
|
430 | |
|
|
431 | my @lines; # read data |
|
|
432 | my $idle_w; |
|
|
433 | my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
|
|
434 | push @lines, scalar <STDIN>; |
|
|
435 | |
|
|
436 | # start an idle watcher, if not already done |
|
|
437 | $idle_w ||= AnyEvent->idle (cb => sub { |
|
|
438 | # handle only one line, when there are lines left |
|
|
439 | if (my $line = shift @lines) { |
|
|
440 | print "handled when idle: $line"; |
|
|
441 | } else { |
|
|
442 | # otherwise disable the idle watcher again |
|
|
443 | undef $idle_w; |
|
|
444 | } |
|
|
445 | }); |
|
|
446 | }); |
253 | |
447 | |
254 | CONDITION VARIABLES |
448 | CONDITION VARIABLES |
|
|
449 | If you are familiar with some event loops you will know that all of them |
|
|
450 | require you to run some blocking "loop", "run" or similar function that |
|
|
451 | will actively watch for new events and call your callbacks. |
|
|
452 | |
|
|
453 | AnyEvent is different, it expects somebody else to run the event loop |
|
|
454 | and will only block when necessary (usually when told by the user). |
|
|
455 | |
|
|
456 | The instrument to do that is called a "condition variable", so called |
|
|
457 | because they represent a condition that must become true. |
|
|
458 | |
255 | Condition variables can be created by calling the "AnyEvent->condvar" |
459 | Condition variables can be created by calling the "AnyEvent->condvar" |
256 | method without any arguments. |
460 | method, usually without arguments. The only argument pair allowed is |
257 | |
461 | |
258 | A condition variable waits for a condition - precisely that the |
462 | "cb", which specifies a callback to be called when the condition |
259 | "->broadcast" method has been called. |
463 | variable becomes true, with the condition variable as the first argument |
|
|
464 | (but not the results). |
260 | |
465 | |
261 | They are very useful to signal that a condition has been fulfilled, for |
466 | After creation, the condition variable is "false" until it becomes |
|
|
467 | "true" by calling the "send" method (or calling the condition variable |
|
|
468 | as if it were a callback, read about the caveats in the description for |
|
|
469 | the "->send" method). |
|
|
470 | |
|
|
471 | Condition variables are similar to callbacks, except that you can |
|
|
472 | optionally wait for them. They can also be called merge points - points |
|
|
473 | in time where multiple outstanding events have been processed. And yet |
|
|
474 | another way to call them is transactions - each condition variable can |
|
|
475 | be used to represent a transaction, which finishes at some point and |
|
|
476 | delivers a result. |
|
|
477 | |
|
|
478 | Condition variables are very useful to signal that something has |
262 | example, if you write a module that does asynchronous http requests, |
479 | finished, for example, if you write a module that does asynchronous http |
263 | then a condition variable would be the ideal candidate to signal the |
480 | requests, then a condition variable would be the ideal candidate to |
264 | availability of results. |
481 | signal the availability of results. The user can either act when the |
|
|
482 | callback is called or can synchronously "->recv" for the results. |
265 | |
483 | |
266 | You can also use condition variables to block your main program until an |
484 | You can also use them to simulate traditional event loops - for example, |
267 | event occurs - for example, you could "->wait" in your main program |
485 | you can block your main program until an event occurs - for example, you |
268 | until the user clicks the Quit button in your app, which would |
486 | could "->recv" in your main program until the user clicks the Quit |
269 | "->broadcast" the "quit" event. |
487 | button of your app, which would "->send" the "quit" event. |
270 | |
488 | |
271 | Note that condition variables recurse into the event loop - if you have |
489 | Note that condition variables recurse into the event loop - if you have |
272 | two pirces of code that call "->wait" in a round-robbin fashion, you |
490 | two pieces of code that call "->recv" in a round-robin fashion, you |
273 | lose. Therefore, condition variables are good to export to your caller, |
491 | lose. Therefore, condition variables are good to export to your caller, |
274 | but you should avoid making a blocking wait yourself, at least in |
492 | but you should avoid making a blocking wait yourself, at least in |
275 | callbacks, as this asks for trouble. |
493 | callbacks, as this asks for trouble. |
276 | |
494 | |
277 | This object has two methods: |
495 | Condition variables are represented by hash refs in perl, and the keys |
|
|
496 | used by AnyEvent itself are all named "_ae_XXX" to make subclassing easy |
|
|
497 | (it is often useful to build your own transaction class on top of |
|
|
498 | AnyEvent). To subclass, use "AnyEvent::CondVar" as base class and call |
|
|
499 | it's "new" method in your own "new" method. |
278 | |
500 | |
279 | $cv->wait |
501 | There are two "sides" to a condition variable - the "producer side" |
|
|
502 | which eventually calls "-> send", and the "consumer side", which waits |
|
|
503 | for the send to occur. |
|
|
504 | |
|
|
505 | Example: wait for a timer. |
|
|
506 | |
|
|
507 | # wait till the result is ready |
|
|
508 | my $result_ready = AnyEvent->condvar; |
|
|
509 | |
|
|
510 | # do something such as adding a timer |
|
|
511 | # or socket watcher the calls $result_ready->send |
|
|
512 | # when the "result" is ready. |
|
|
513 | # in this case, we simply use a timer: |
|
|
514 | my $w = AnyEvent->timer ( |
|
|
515 | after => 1, |
|
|
516 | cb => sub { $result_ready->send }, |
|
|
517 | ); |
|
|
518 | |
|
|
519 | # this "blocks" (while handling events) till the callback |
|
|
520 | # calls send |
|
|
521 | $result_ready->recv; |
|
|
522 | |
|
|
523 | Example: wait for a timer, but take advantage of the fact that condition |
|
|
524 | variables are also code references. |
|
|
525 | |
|
|
526 | my $done = AnyEvent->condvar; |
|
|
527 | my $delay = AnyEvent->timer (after => 5, cb => $done); |
|
|
528 | $done->recv; |
|
|
529 | |
|
|
530 | Example: Imagine an API that returns a condvar and doesn't support |
|
|
531 | callbacks. This is how you make a synchronous call, for example from the |
|
|
532 | main program: |
|
|
533 | |
|
|
534 | use AnyEvent::CouchDB; |
|
|
535 | |
|
|
536 | ... |
|
|
537 | |
|
|
538 | my @info = $couchdb->info->recv; |
|
|
539 | |
|
|
540 | And this is how you would just ste a callback to be called whenever the |
|
|
541 | results are available: |
|
|
542 | |
|
|
543 | $couchdb->info->cb (sub { |
|
|
544 | my @info = $_[0]->recv; |
|
|
545 | }); |
|
|
546 | |
|
|
547 | METHODS FOR PRODUCERS |
|
|
548 | These methods should only be used by the producing side, i.e. the |
|
|
549 | code/module that eventually sends the signal. Note that it is also the |
|
|
550 | producer side which creates the condvar in most cases, but it isn't |
|
|
551 | uncommon for the consumer to create it as well. |
|
|
552 | |
|
|
553 | $cv->send (...) |
|
|
554 | Flag the condition as ready - a running "->recv" and all further |
|
|
555 | calls to "recv" will (eventually) return after this method has been |
|
|
556 | called. If nobody is waiting the send will be remembered. |
|
|
557 | |
|
|
558 | If a callback has been set on the condition variable, it is called |
|
|
559 | immediately from within send. |
|
|
560 | |
|
|
561 | Any arguments passed to the "send" call will be returned by all |
|
|
562 | future "->recv" calls. |
|
|
563 | |
|
|
564 | Condition variables are overloaded so one can call them directly (as |
|
|
565 | a code reference). Calling them directly is the same as calling |
|
|
566 | "send". Note, however, that many C-based event loops do not handle |
|
|
567 | overloading, so as tempting as it may be, passing a condition |
|
|
568 | variable instead of a callback does not work. Both the pure perl and |
|
|
569 | EV loops support overloading, however, as well as all functions that |
|
|
570 | use perl to invoke a callback (as in AnyEvent::Socket and |
|
|
571 | AnyEvent::DNS for example). |
|
|
572 | |
|
|
573 | $cv->croak ($error) |
|
|
574 | Similar to send, but causes all call's to "->recv" to invoke |
|
|
575 | "Carp::croak" with the given error message/object/scalar. |
|
|
576 | |
|
|
577 | This can be used to signal any errors to the condition variable |
|
|
578 | user/consumer. |
|
|
579 | |
|
|
580 | $cv->begin ([group callback]) |
|
|
581 | $cv->end |
|
|
582 | These two methods can be used to combine many transactions/events |
|
|
583 | into one. For example, a function that pings many hosts in parallel |
|
|
584 | might want to use a condition variable for the whole process. |
|
|
585 | |
|
|
586 | Every call to "->begin" will increment a counter, and every call to |
|
|
587 | "->end" will decrement it. If the counter reaches 0 in "->end", the |
|
|
588 | (last) callback passed to "begin" will be executed. That callback is |
|
|
589 | *supposed* to call "->send", but that is not required. If no |
|
|
590 | callback was set, "send" will be called without any arguments. |
|
|
591 | |
|
|
592 | You can think of "$cv->send" giving you an OR condition (one call |
|
|
593 | sends), while "$cv->begin" and "$cv->end" giving you an AND |
|
|
594 | condition (all "begin" calls must be "end"'ed before the condvar |
|
|
595 | sends). |
|
|
596 | |
|
|
597 | Let's start with a simple example: you have two I/O watchers (for |
|
|
598 | example, STDOUT and STDERR for a program), and you want to wait for |
|
|
599 | both streams to close before activating a condvar: |
|
|
600 | |
|
|
601 | my $cv = AnyEvent->condvar; |
|
|
602 | |
|
|
603 | $cv->begin; # first watcher |
|
|
604 | my $w1 = AnyEvent->io (fh => $fh1, cb => sub { |
|
|
605 | defined sysread $fh1, my $buf, 4096 |
|
|
606 | or $cv->end; |
|
|
607 | }); |
|
|
608 | |
|
|
609 | $cv->begin; # second watcher |
|
|
610 | my $w2 = AnyEvent->io (fh => $fh2, cb => sub { |
|
|
611 | defined sysread $fh2, my $buf, 4096 |
|
|
612 | or $cv->end; |
|
|
613 | }); |
|
|
614 | |
|
|
615 | $cv->recv; |
|
|
616 | |
|
|
617 | This works because for every event source (EOF on file handle), |
|
|
618 | there is one call to "begin", so the condvar waits for all calls to |
|
|
619 | "end" before sending. |
|
|
620 | |
|
|
621 | The ping example mentioned above is slightly more complicated, as |
|
|
622 | the there are results to be passwd back, and the number of tasks |
|
|
623 | that are begung can potentially be zero: |
|
|
624 | |
|
|
625 | my $cv = AnyEvent->condvar; |
|
|
626 | |
|
|
627 | my %result; |
|
|
628 | $cv->begin (sub { $cv->send (\%result) }); |
|
|
629 | |
|
|
630 | for my $host (@list_of_hosts) { |
|
|
631 | $cv->begin; |
|
|
632 | ping_host_then_call_callback $host, sub { |
|
|
633 | $result{$host} = ...; |
|
|
634 | $cv->end; |
|
|
635 | }; |
|
|
636 | } |
|
|
637 | |
|
|
638 | $cv->end; |
|
|
639 | |
|
|
640 | This code fragment supposedly pings a number of hosts and calls |
|
|
641 | "send" after results for all then have have been gathered - in any |
|
|
642 | order. To achieve this, the code issues a call to "begin" when it |
|
|
643 | starts each ping request and calls "end" when it has received some |
|
|
644 | result for it. Since "begin" and "end" only maintain a counter, the |
|
|
645 | order in which results arrive is not relevant. |
|
|
646 | |
|
|
647 | There is an additional bracketing call to "begin" and "end" outside |
|
|
648 | the loop, which serves two important purposes: first, it sets the |
|
|
649 | callback to be called once the counter reaches 0, and second, it |
|
|
650 | ensures that "send" is called even when "no" hosts are being pinged |
|
|
651 | (the loop doesn't execute once). |
|
|
652 | |
|
|
653 | This is the general pattern when you "fan out" into multiple (but |
|
|
654 | potentially none) subrequests: use an outer "begin"/"end" pair to |
|
|
655 | set the callback and ensure "end" is called at least once, and then, |
|
|
656 | for each subrequest you start, call "begin" and for each subrequest |
|
|
657 | you finish, call "end". |
|
|
658 | |
|
|
659 | METHODS FOR CONSUMERS |
|
|
660 | These methods should only be used by the consuming side, i.e. the code |
|
|
661 | awaits the condition. |
|
|
662 | |
|
|
663 | $cv->recv |
280 | Wait (blocking if necessary) until the "->broadcast" method has been |
664 | Wait (blocking if necessary) until the "->send" or "->croak" methods |
281 | called on c<$cv>, while servicing other watchers normally. |
665 | have been called on c<$cv>, while servicing other watchers normally. |
282 | |
666 | |
283 | You can only wait once on a condition - additional calls will return |
667 | You can only wait once on a condition - additional calls are valid |
284 | immediately. |
668 | but will return immediately. |
|
|
669 | |
|
|
670 | If an error condition has been set by calling "->croak", then this |
|
|
671 | function will call "croak". |
|
|
672 | |
|
|
673 | In list context, all parameters passed to "send" will be returned, |
|
|
674 | in scalar context only the first one will be returned. |
285 | |
675 | |
286 | Not all event models support a blocking wait - some die in that case |
676 | Not all event models support a blocking wait - some die in that case |
287 | (programs might want to do that to stay interactive), so *if you are |
677 | (programs might want to do that to stay interactive), so *if you are |
288 | using this from a module, never require a blocking wait*, but let |
678 | using this from a module, never require a blocking wait*, but let |
289 | the caller decide whether the call will block or not (for example, |
679 | the caller decide whether the call will block or not (for example, |
290 | by coupling condition variables with some kind of request results |
680 | by coupling condition variables with some kind of request results |
291 | and supporting callbacks so the caller knows that getting the result |
681 | and supporting callbacks so the caller knows that getting the result |
292 | will not block, while still suppporting blocking waits if the caller |
682 | will not block, while still supporting blocking waits if the caller |
293 | so desires). |
683 | so desires). |
294 | |
684 | |
295 | Another reason *never* to "->wait" in a module is that you cannot |
685 | Another reason *never* to "->recv" in a module is that you cannot |
296 | sensibly have two "->wait"'s in parallel, as that would require |
686 | sensibly have two "->recv"'s in parallel, as that would require |
297 | multiple interpreters or coroutines/threads, none of which |
687 | multiple interpreters or coroutines/threads, none of which |
298 | "AnyEvent" can supply (the coroutine-aware backends |
688 | "AnyEvent" can supply. |
299 | AnyEvent::Impl::CoroEV and AnyEvent::Impl::CoroEvent explicitly |
|
|
300 | support concurrent "->wait"'s from different coroutines, however). |
|
|
301 | |
689 | |
302 | $cv->broadcast |
690 | The Coro module, however, *can* and *does* supply coroutines and, in |
303 | Flag the condition as ready - a running "->wait" and all further |
691 | fact, Coro::AnyEvent replaces AnyEvent's condvars by coroutine-safe |
304 | calls to "wait" will (eventually) return after this method has been |
692 | versions and also integrates coroutines into AnyEvent, making |
305 | called. If nobody is waiting the broadcast will be remembered.. |
693 | blocking "->recv" calls perfectly safe as long as they are done from |
|
|
694 | another coroutine (one that doesn't run the event loop). |
306 | |
695 | |
307 | Example: |
696 | You can ensure that "-recv" never blocks by setting a callback and |
|
|
697 | only calling "->recv" from within that callback (or at a later |
|
|
698 | time). This will work even when the event loop does not support |
|
|
699 | blocking waits otherwise. |
308 | |
700 | |
309 | # wait till the result is ready |
701 | $bool = $cv->ready |
310 | my $result_ready = AnyEvent->condvar; |
702 | Returns true when the condition is "true", i.e. whether "send" or |
|
|
703 | "croak" have been called. |
311 | |
704 | |
312 | # do something such as adding a timer |
705 | $cb = $cv->cb ($cb->($cv)) |
313 | # or socket watcher the calls $result_ready->broadcast |
706 | This is a mutator function that returns the callback set and |
314 | # when the "result" is ready. |
707 | optionally replaces it before doing so. |
315 | # in this case, we simply use a timer: |
|
|
316 | my $w = AnyEvent->timer ( |
|
|
317 | after => 1, |
|
|
318 | cb => sub { $result_ready->broadcast }, |
|
|
319 | ); |
|
|
320 | |
708 | |
321 | # this "blocks" (while handling events) till the watcher |
709 | The callback will be called when the condition becomes "true", i.e. |
322 | # calls broadcast |
710 | when "send" or "croak" are called, with the only argument being the |
323 | $result_ready->wait; |
711 | condition variable itself. Calling "recv" inside the callback or at |
|
|
712 | any later time is guaranteed not to block. |
|
|
713 | |
|
|
714 | SUPPORTED EVENT LOOPS/BACKENDS |
|
|
715 | The available backend classes are (every class has its own manpage): |
|
|
716 | |
|
|
717 | Backends that are autoprobed when no other event loop can be found. |
|
|
718 | EV is the preferred backend when no other event loop seems to be in |
|
|
719 | use. If EV is not installed, then AnyEvent will try Event, and, |
|
|
720 | failing that, will fall back to its own pure-perl implementation, |
|
|
721 | which is available everywhere as it comes with AnyEvent itself. |
|
|
722 | |
|
|
723 | AnyEvent::Impl::EV based on EV (interface to libev, best choice). |
|
|
724 | AnyEvent::Impl::Event based on Event, very stable, few glitches. |
|
|
725 | AnyEvent::Impl::Perl pure-perl implementation, fast and portable. |
|
|
726 | |
|
|
727 | Backends that are transparently being picked up when they are used. |
|
|
728 | These will be used when they are currently loaded when the first |
|
|
729 | watcher is created, in which case it is assumed that the application |
|
|
730 | is using them. This means that AnyEvent will automatically pick the |
|
|
731 | right backend when the main program loads an event module before |
|
|
732 | anything starts to create watchers. Nothing special needs to be done |
|
|
733 | by the main program. |
|
|
734 | |
|
|
735 | AnyEvent::Impl::Glib based on Glib, slow but very stable. |
|
|
736 | AnyEvent::Impl::Tk based on Tk, very broken. |
|
|
737 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
|
|
738 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
|
|
739 | |
|
|
740 | Backends with special needs. |
|
|
741 | Qt requires the Qt::Application to be instantiated first, but will |
|
|
742 | otherwise be picked up automatically. As long as the main program |
|
|
743 | instantiates the application before any AnyEvent watchers are |
|
|
744 | created, everything should just work. |
|
|
745 | |
|
|
746 | AnyEvent::Impl::Qt based on Qt. |
|
|
747 | |
|
|
748 | Support for IO::Async can only be partial, as it is too broken and |
|
|
749 | architecturally limited to even support the AnyEvent API. It also is |
|
|
750 | the only event loop that needs the loop to be set explicitly, so it |
|
|
751 | can only be used by a main program knowing about AnyEvent. See |
|
|
752 | AnyEvent::Impl::Async for the gory details. |
|
|
753 | |
|
|
754 | AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed. |
|
|
755 | |
|
|
756 | Event loops that are indirectly supported via other backends. |
|
|
757 | Some event loops can be supported via other modules: |
|
|
758 | |
|
|
759 | There is no direct support for WxWidgets (Wx) or Prima. |
|
|
760 | |
|
|
761 | WxWidgets has no support for watching file handles. However, you can |
|
|
762 | use WxWidgets through the POE adaptor, as POE has a Wx backend that |
|
|
763 | simply polls 20 times per second, which was considered to be too |
|
|
764 | horrible to even consider for AnyEvent. |
|
|
765 | |
|
|
766 | Prima is not supported as nobody seems to be using it, but it has a |
|
|
767 | POE backend, so it can be supported through POE. |
|
|
768 | |
|
|
769 | AnyEvent knows about both Prima and Wx, however, and will try to |
|
|
770 | load POE when detecting them, in the hope that POE will pick them |
|
|
771 | up, in which case everything will be automatic. |
324 | |
772 | |
325 | GLOBAL VARIABLES AND FUNCTIONS |
773 | GLOBAL VARIABLES AND FUNCTIONS |
|
|
774 | These are not normally required to use AnyEvent, but can be useful to |
|
|
775 | write AnyEvent extension modules. |
|
|
776 | |
326 | $AnyEvent::MODEL |
777 | $AnyEvent::MODEL |
327 | Contains "undef" until the first watcher is being created. Then it |
778 | Contains "undef" until the first watcher is being created, before |
|
|
779 | the backend has been autodetected. |
|
|
780 | |
328 | contains the event model that is being used, which is the name of |
781 | Afterwards it contains the event model that is being used, which is |
329 | the Perl class implementing the model. This class is usually one of |
782 | the name of the Perl class implementing the model. This class is |
330 | the "AnyEvent::Impl:xxx" modules, but can be any other class in the |
783 | usually one of the "AnyEvent::Impl:xxx" modules, but can be any |
331 | case AnyEvent has been extended at runtime (e.g. in *rxvt-unicode*). |
784 | other class in the case AnyEvent has been extended at runtime (e.g. |
332 | |
785 | in *rxvt-unicode* it will be "urxvt::anyevent"). |
333 | The known classes so far are: |
|
|
334 | |
|
|
335 | AnyEvent::Impl::CoroEV based on Coro::EV, best choice. |
|
|
336 | AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice. |
|
|
337 | AnyEvent::Impl::EV based on EV (an interface to libev, also best choice). |
|
|
338 | AnyEvent::Impl::Event based on Event, also second best choice :) |
|
|
339 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
|
|
340 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
|
|
341 | AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable. |
|
|
342 | |
786 | |
343 | AnyEvent::detect |
787 | AnyEvent::detect |
344 | Returns $AnyEvent::MODEL, forcing autodetection of the event model |
788 | Returns $AnyEvent::MODEL, forcing autodetection of the event model |
345 | if necessary. You should only call this function right before you |
789 | if necessary. You should only call this function right before you |
346 | would have created an AnyEvent watcher anyway, that is, as late as |
790 | would have created an AnyEvent watcher anyway, that is, as late as |
347 | possible at runtime. |
791 | possible at runtime, and not e.g. while initialising of your module. |
|
|
792 | |
|
|
793 | If you need to do some initialisation before AnyEvent watchers are |
|
|
794 | created, use "post_detect". |
|
|
795 | |
|
|
796 | $guard = AnyEvent::post_detect { BLOCK } |
|
|
797 | Arranges for the code block to be executed as soon as the event |
|
|
798 | model is autodetected (or immediately if this has already happened). |
|
|
799 | |
|
|
800 | The block will be executed *after* the actual backend has been |
|
|
801 | detected ($AnyEvent::MODEL is set), but *before* any watchers have |
|
|
802 | been created, so it is possible to e.g. patch @AnyEvent::ISA or do |
|
|
803 | other initialisations - see the sources of AnyEvent::Strict or |
|
|
804 | AnyEvent::AIO to see how this is used. |
|
|
805 | |
|
|
806 | The most common usage is to create some global watchers, without |
|
|
807 | forcing event module detection too early, for example, AnyEvent::AIO |
|
|
808 | creates and installs the global IO::AIO watcher in a "post_detect" |
|
|
809 | block to avoid autodetecting the event module at load time. |
|
|
810 | |
|
|
811 | If called in scalar or list context, then it creates and returns an |
|
|
812 | object that automatically removes the callback again when it is |
|
|
813 | destroyed. See Coro::BDB for a case where this is useful. |
|
|
814 | |
|
|
815 | @AnyEvent::post_detect |
|
|
816 | If there are any code references in this array (you can "push" to it |
|
|
817 | before or after loading AnyEvent), then they will called directly |
|
|
818 | after the event loop has been chosen. |
|
|
819 | |
|
|
820 | You should check $AnyEvent::MODEL before adding to this array, |
|
|
821 | though: if it is defined then the event loop has already been |
|
|
822 | detected, and the array will be ignored. |
|
|
823 | |
|
|
824 | Best use "AnyEvent::post_detect { BLOCK }" when your application |
|
|
825 | allows it,as it takes care of these details. |
|
|
826 | |
|
|
827 | This variable is mainly useful for modules that can do something |
|
|
828 | useful when AnyEvent is used and thus want to know when it is |
|
|
829 | initialised, but do not need to even load it by default. This array |
|
|
830 | provides the means to hook into AnyEvent passively, without loading |
|
|
831 | it. |
348 | |
832 | |
349 | WHAT TO DO IN A MODULE |
833 | WHAT TO DO IN A MODULE |
350 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
834 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
351 | freely, but you should not load a specific event module or rely on it. |
835 | freely, but you should not load a specific event module or rely on it. |
352 | |
836 | |
353 | Be careful when you create watchers in the module body - AnyEvent will |
837 | Be careful when you create watchers in the module body - AnyEvent will |
354 | decide which event module to use as soon as the first method is called, |
838 | decide which event module to use as soon as the first method is called, |
355 | so by calling AnyEvent in your module body you force the user of your |
839 | so by calling AnyEvent in your module body you force the user of your |
356 | module to load the event module first. |
840 | module to load the event module first. |
357 | |
841 | |
358 | Never call "->wait" on a condition variable unless you *know* that the |
842 | Never call "->recv" on a condition variable unless you *know* that the |
359 | "->broadcast" method has been called on it already. This is because it |
843 | "->send" method has been called on it already. This is because it will |
360 | will stall the whole program, and the whole point of using events is to |
844 | stall the whole program, and the whole point of using events is to stay |
361 | stay interactive. |
845 | interactive. |
362 | |
846 | |
363 | It is fine, however, to call "->wait" when the user of your module |
847 | It is fine, however, to call "->recv" when the user of your module |
364 | requests it (i.e. if you create a http request object ad have a method |
848 | requests it (i.e. if you create a http request object ad have a method |
365 | called "results" that returns the results, it should call "->wait" |
849 | called "results" that returns the results, it should call "->recv" |
366 | freely, as the user of your module knows what she is doing. always). |
850 | freely, as the user of your module knows what she is doing. always). |
367 | |
851 | |
368 | WHAT TO DO IN THE MAIN PROGRAM |
852 | WHAT TO DO IN THE MAIN PROGRAM |
369 | There will always be a single main program - the only place that should |
853 | There will always be a single main program - the only place that should |
370 | dictate which event model to use. |
854 | dictate which event model to use. |
… | |
… | |
372 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
856 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
373 | do anything special (it does not need to be event-based) and let |
857 | do anything special (it does not need to be event-based) and let |
374 | AnyEvent decide which implementation to chose if some module relies on |
858 | AnyEvent decide which implementation to chose if some module relies on |
375 | it. |
859 | it. |
376 | |
860 | |
377 | If the main program relies on a specific event model. For example, in |
861 | If the main program relies on a specific event model - for example, in |
378 | Gtk2 programs you have to rely on the Glib module. You should load the |
862 | Gtk2 programs you have to rely on the Glib module - you should load the |
379 | event module before loading AnyEvent or any module that uses it: |
863 | event module before loading AnyEvent or any module that uses it: |
380 | generally speaking, you should load it as early as possible. The reason |
864 | generally speaking, you should load it as early as possible. The reason |
381 | is that modules might create watchers when they are loaded, and AnyEvent |
865 | is that modules might create watchers when they are loaded, and AnyEvent |
382 | will decide on the event model to use as soon as it creates watchers, |
866 | will decide on the event model to use as soon as it creates watchers, |
383 | and it might chose the wrong one unless you load the correct one |
867 | and it might chose the wrong one unless you load the correct one |
384 | yourself. |
868 | yourself. |
385 | |
869 | |
386 | You can chose to use a rather inefficient pure-perl implementation by |
870 | You can chose to use a pure-perl implementation by loading the |
387 | loading the "AnyEvent::Impl::Perl" module, which gives you similar |
871 | "AnyEvent::Impl::Perl" module, which gives you similar behaviour |
388 | behaviour everywhere, but letting AnyEvent chose is generally better. |
872 | everywhere, but letting AnyEvent chose the model is generally better. |
|
|
873 | |
|
|
874 | MAINLOOP EMULATION |
|
|
875 | Sometimes (often for short test scripts, or even standalone programs who |
|
|
876 | only want to use AnyEvent), you do not want to run a specific event |
|
|
877 | loop. |
|
|
878 | |
|
|
879 | In that case, you can use a condition variable like this: |
|
|
880 | |
|
|
881 | AnyEvent->condvar->recv; |
|
|
882 | |
|
|
883 | This has the effect of entering the event loop and looping forever. |
|
|
884 | |
|
|
885 | Note that usually your program has some exit condition, in which case it |
|
|
886 | is better to use the "traditional" approach of storing a condition |
|
|
887 | variable somewhere, waiting for it, and sending it when the program |
|
|
888 | should exit cleanly. |
|
|
889 | |
|
|
890 | OTHER MODULES |
|
|
891 | The following is a non-exhaustive list of additional modules that use |
|
|
892 | AnyEvent as a client and can therefore be mixed easily with other |
|
|
893 | AnyEvent modules and other event loops in the same program. Some of the |
|
|
894 | modules come with AnyEvent, most are available via CPAN. |
|
|
895 | |
|
|
896 | AnyEvent::Util |
|
|
897 | Contains various utility functions that replace often-used but |
|
|
898 | blocking functions such as "inet_aton" by event-/callback-based |
|
|
899 | versions. |
|
|
900 | |
|
|
901 | AnyEvent::Socket |
|
|
902 | Provides various utility functions for (internet protocol) sockets, |
|
|
903 | addresses and name resolution. Also functions to create non-blocking |
|
|
904 | tcp connections or tcp servers, with IPv6 and SRV record support and |
|
|
905 | more. |
|
|
906 | |
|
|
907 | AnyEvent::Handle |
|
|
908 | Provide read and write buffers, manages watchers for reads and |
|
|
909 | writes, supports raw and formatted I/O, I/O queued and fully |
|
|
910 | transparent and non-blocking SSL/TLS (via AnyEvent::TLS. |
|
|
911 | |
|
|
912 | AnyEvent::DNS |
|
|
913 | Provides rich asynchronous DNS resolver capabilities. |
|
|
914 | |
|
|
915 | AnyEvent::HTTP |
|
|
916 | A simple-to-use HTTP library that is capable of making a lot of |
|
|
917 | concurrent HTTP requests. |
|
|
918 | |
|
|
919 | AnyEvent::HTTPD |
|
|
920 | Provides a simple web application server framework. |
|
|
921 | |
|
|
922 | AnyEvent::FastPing |
|
|
923 | The fastest ping in the west. |
|
|
924 | |
|
|
925 | AnyEvent::DBI |
|
|
926 | Executes DBI requests asynchronously in a proxy process. |
|
|
927 | |
|
|
928 | AnyEvent::AIO |
|
|
929 | Truly asynchronous I/O, should be in the toolbox of every event |
|
|
930 | programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent |
|
|
931 | together. |
|
|
932 | |
|
|
933 | AnyEvent::BDB |
|
|
934 | Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently |
|
|
935 | fuses BDB and AnyEvent together. |
|
|
936 | |
|
|
937 | AnyEvent::GPSD |
|
|
938 | A non-blocking interface to gpsd, a daemon delivering GPS |
|
|
939 | information. |
|
|
940 | |
|
|
941 | AnyEvent::IRC |
|
|
942 | AnyEvent based IRC client module family (replacing the older |
|
|
943 | Net::IRC3). |
|
|
944 | |
|
|
945 | AnyEvent::XMPP |
|
|
946 | AnyEvent based XMPP (Jabber protocol) module family (replacing the |
|
|
947 | older Net::XMPP2>. |
|
|
948 | |
|
|
949 | AnyEvent::IGS |
|
|
950 | A non-blocking interface to the Internet Go Server protocol (used by |
|
|
951 | App::IGS). |
|
|
952 | |
|
|
953 | Net::FCP |
|
|
954 | AnyEvent-based implementation of the Freenet Client Protocol, |
|
|
955 | birthplace of AnyEvent. |
|
|
956 | |
|
|
957 | Event::ExecFlow |
|
|
958 | High level API for event-based execution flow control. |
|
|
959 | |
|
|
960 | Coro |
|
|
961 | Has special support for AnyEvent via Coro::AnyEvent. |
|
|
962 | |
|
|
963 | ERROR AND EXCEPTION HANDLING |
|
|
964 | In general, AnyEvent does not do any error handling - it relies on the |
|
|
965 | caller to do that if required. The AnyEvent::Strict module (see also the |
|
|
966 | "PERL_ANYEVENT_STRICT" environment variable, below) provides strict |
|
|
967 | checking of all AnyEvent methods, however, which is highly useful during |
|
|
968 | development. |
|
|
969 | |
|
|
970 | As for exception handling (i.e. runtime errors and exceptions thrown |
|
|
971 | while executing a callback), this is not only highly event-loop |
|
|
972 | specific, but also not in any way wrapped by this module, as this is the |
|
|
973 | job of the main program. |
|
|
974 | |
|
|
975 | The pure perl event loop simply re-throws the exception (usually within |
|
|
976 | "condvar->recv"), the Event and EV modules call "$Event/EV::DIED->()", |
|
|
977 | Glib uses "install_exception_handler" and so on. |
|
|
978 | |
|
|
979 | ENVIRONMENT VARIABLES |
|
|
980 | The following environment variables are used by this module or its |
|
|
981 | submodules. |
|
|
982 | |
|
|
983 | Note that AnyEvent will remove *all* environment variables starting with |
|
|
984 | "PERL_ANYEVENT_" from %ENV when it is loaded while taint mode is |
|
|
985 | enabled. |
|
|
986 | |
|
|
987 | "PERL_ANYEVENT_VERBOSE" |
|
|
988 | By default, AnyEvent will be completely silent except in fatal |
|
|
989 | conditions. You can set this environment variable to make AnyEvent |
|
|
990 | more talkative. |
|
|
991 | |
|
|
992 | When set to 1 or higher, causes AnyEvent to warn about unexpected |
|
|
993 | conditions, such as not being able to load the event model specified |
|
|
994 | by "PERL_ANYEVENT_MODEL". |
|
|
995 | |
|
|
996 | When set to 2 or higher, cause AnyEvent to report to STDERR which |
|
|
997 | event model it chooses. |
|
|
998 | |
|
|
999 | "PERL_ANYEVENT_STRICT" |
|
|
1000 | AnyEvent does not do much argument checking by default, as thorough |
|
|
1001 | argument checking is very costly. Setting this variable to a true |
|
|
1002 | value will cause AnyEvent to load "AnyEvent::Strict" and then to |
|
|
1003 | thoroughly check the arguments passed to most method calls. If it |
|
|
1004 | finds any problems, it will croak. |
|
|
1005 | |
|
|
1006 | In other words, enables "strict" mode. |
|
|
1007 | |
|
|
1008 | Unlike "use strict", it is definitely recommended to keep it off in |
|
|
1009 | production. Keeping "PERL_ANYEVENT_STRICT=1" in your environment |
|
|
1010 | while developing programs can be very useful, however. |
|
|
1011 | |
|
|
1012 | "PERL_ANYEVENT_MODEL" |
|
|
1013 | This can be used to specify the event model to be used by AnyEvent, |
|
|
1014 | before auto detection and -probing kicks in. It must be a string |
|
|
1015 | consisting entirely of ASCII letters. The string "AnyEvent::Impl::" |
|
|
1016 | gets prepended and the resulting module name is loaded and if the |
|
|
1017 | load was successful, used as event model. If it fails to load |
|
|
1018 | AnyEvent will proceed with auto detection and -probing. |
|
|
1019 | |
|
|
1020 | This functionality might change in future versions. |
|
|
1021 | |
|
|
1022 | For example, to force the pure perl model (AnyEvent::Impl::Perl) you |
|
|
1023 | could start your program like this: |
|
|
1024 | |
|
|
1025 | PERL_ANYEVENT_MODEL=Perl perl ... |
|
|
1026 | |
|
|
1027 | "PERL_ANYEVENT_PROTOCOLS" |
|
|
1028 | Used by both AnyEvent::DNS and AnyEvent::Socket to determine |
|
|
1029 | preferences for IPv4 or IPv6. The default is unspecified (and might |
|
|
1030 | change, or be the result of auto probing). |
|
|
1031 | |
|
|
1032 | Must be set to a comma-separated list of protocols or address |
|
|
1033 | families, current supported: "ipv4" and "ipv6". Only protocols |
|
|
1034 | mentioned will be used, and preference will be given to protocols |
|
|
1035 | mentioned earlier in the list. |
|
|
1036 | |
|
|
1037 | This variable can effectively be used for denial-of-service attacks |
|
|
1038 | against local programs (e.g. when setuid), although the impact is |
|
|
1039 | likely small, as the program has to handle conenction and other |
|
|
1040 | failures anyways. |
|
|
1041 | |
|
|
1042 | Examples: "PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6" - prefer IPv4 over |
|
|
1043 | IPv6, but support both and try to use both. |
|
|
1044 | "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to |
|
|
1045 | resolve or contact IPv6 addresses. |
|
|
1046 | "PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4" support either IPv4 or IPv6, but |
|
|
1047 | prefer IPv6 over IPv4. |
|
|
1048 | |
|
|
1049 | "PERL_ANYEVENT_EDNS0" |
|
|
1050 | Used by AnyEvent::DNS to decide whether to use the EDNS0 extension |
|
|
1051 | for DNS. This extension is generally useful to reduce DNS traffic, |
|
|
1052 | but some (broken) firewalls drop such DNS packets, which is why it |
|
|
1053 | is off by default. |
|
|
1054 | |
|
|
1055 | Setting this variable to 1 will cause AnyEvent::DNS to announce |
|
|
1056 | EDNS0 in its DNS requests. |
|
|
1057 | |
|
|
1058 | "PERL_ANYEVENT_MAX_FORKS" |
|
|
1059 | The maximum number of child processes that |
|
|
1060 | "AnyEvent::Util::fork_call" will create in parallel. |
|
|
1061 | |
|
|
1062 | "PERL_ANYEVENT_MAX_OUTSTANDING_DNS" |
|
|
1063 | The default value for the "max_outstanding" parameter for the |
|
|
1064 | default DNS resolver - this is the maximum number of parallel DNS |
|
|
1065 | requests that are sent to the DNS server. |
|
|
1066 | |
|
|
1067 | "PERL_ANYEVENT_RESOLV_CONF" |
|
|
1068 | The file to use instead of /etc/resolv.conf (or OS-specific |
|
|
1069 | configuration) in the default resolver. When set to the empty |
|
|
1070 | string, no default config will be used. |
|
|
1071 | |
|
|
1072 | "PERL_ANYEVENT_CA_FILE", "PERL_ANYEVENT_CA_PATH". |
|
|
1073 | When neither "ca_file" nor "ca_path" was specified during |
|
|
1074 | AnyEvent::TLS context creation, and either of these environment |
|
|
1075 | variables exist, they will be used to specify CA certificate |
|
|
1076 | locations instead of a system-dependent default. |
389 | |
1077 | |
390 | SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
1078 | SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
391 | This is an advanced topic that you do not normally need to use AnyEvent |
1079 | This is an advanced topic that you do not normally need to use AnyEvent |
392 | in a module. This section is only of use to event loop authors who want |
1080 | in a module. This section is only of use to event loop authors who want |
393 | to provide AnyEvent compatibility. |
1081 | to provide AnyEvent compatibility. |
… | |
… | |
428 | *rxvt-unicode* also cheats a bit by not providing blocking access to |
1116 | *rxvt-unicode* also cheats a bit by not providing blocking access to |
429 | condition variables: code blocking while waiting for a condition will |
1117 | condition variables: code blocking while waiting for a condition will |
430 | "die". This still works with most modules/usages, and blocking calls |
1118 | "die". This still works with most modules/usages, and blocking calls |
431 | must not be done in an interactive application, so it makes sense. |
1119 | must not be done in an interactive application, so it makes sense. |
432 | |
1120 | |
433 | ENVIRONMENT VARIABLES |
|
|
434 | The following environment variables are used by this module: |
|
|
435 | |
|
|
436 | "PERL_ANYEVENT_VERBOSE" when set to 2 or higher, cause AnyEvent to |
|
|
437 | report to STDERR which event model it chooses. |
|
|
438 | |
|
|
439 | EXAMPLE PROGRAM |
1121 | EXAMPLE PROGRAM |
440 | The following program uses an IO watcher to read data from STDIN, a |
1122 | The following program uses an I/O watcher to read data from STDIN, a |
441 | timer to display a message once per second, and a condition variable to |
1123 | timer to display a message once per second, and a condition variable to |
442 | quit the program when the user enters quit: |
1124 | quit the program when the user enters quit: |
443 | |
1125 | |
444 | use AnyEvent; |
1126 | use AnyEvent; |
445 | |
1127 | |
… | |
… | |
450 | poll => 'r', |
1132 | poll => 'r', |
451 | cb => sub { |
1133 | cb => sub { |
452 | warn "io event <$_[0]>\n"; # will always output <r> |
1134 | warn "io event <$_[0]>\n"; # will always output <r> |
453 | chomp (my $input = <STDIN>); # read a line |
1135 | chomp (my $input = <STDIN>); # read a line |
454 | warn "read: $input\n"; # output what has been read |
1136 | warn "read: $input\n"; # output what has been read |
455 | $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i |
1137 | $cv->send if $input =~ /^q/i; # quit program if /^q/i |
456 | }, |
1138 | }, |
457 | ); |
1139 | ); |
458 | |
1140 | |
459 | my $time_watcher; # can only be used once |
1141 | my $time_watcher; # can only be used once |
460 | |
1142 | |
… | |
… | |
465 | }); |
1147 | }); |
466 | } |
1148 | } |
467 | |
1149 | |
468 | new_timer; # create first timer |
1150 | new_timer; # create first timer |
469 | |
1151 | |
470 | $cv->wait; # wait until user enters /^q/i |
1152 | $cv->recv; # wait until user enters /^q/i |
471 | |
1153 | |
472 | REAL-WORLD EXAMPLE |
1154 | REAL-WORLD EXAMPLE |
473 | Consider the Net::FCP module. It features (among others) the following |
1155 | Consider the Net::FCP module. It features (among others) the following |
474 | API calls, which are to freenet what HTTP GET requests are to http: |
1156 | API calls, which are to freenet what HTTP GET requests are to http: |
475 | |
1157 | |
… | |
… | |
524 | syswrite $txn->{fh}, $txn->{request} |
1206 | syswrite $txn->{fh}, $txn->{request} |
525 | or die "connection or write error"; |
1207 | or die "connection or write error"; |
526 | $txn->{w} = AnyEvent->io (fh => $txn->{fh}, poll => 'r', cb => sub { $txn->fh_ready_r }); |
1208 | $txn->{w} = AnyEvent->io (fh => $txn->{fh}, poll => 'r', cb => sub { $txn->fh_ready_r }); |
527 | |
1209 | |
528 | Again, "fh_ready_r" waits till all data has arrived, and then stores the |
1210 | Again, "fh_ready_r" waits till all data has arrived, and then stores the |
529 | result and signals any possible waiters that the request ahs finished: |
1211 | result and signals any possible waiters that the request has finished: |
530 | |
1212 | |
531 | sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf}; |
1213 | sysread $txn->{fh}, $txn->{buf}, length $txn->{$buf}; |
532 | |
1214 | |
533 | if (end-of-file or data complete) { |
1215 | if (end-of-file or data complete) { |
534 | $txn->{result} = $txn->{buf}; |
1216 | $txn->{result} = $txn->{buf}; |
535 | $txn->{finished}->broadcast; |
1217 | $txn->{finished}->send; |
536 | $txb->{cb}->($txn) of $txn->{cb}; # also call callback |
1218 | $txb->{cb}->($txn) of $txn->{cb}; # also call callback |
537 | } |
1219 | } |
538 | |
1220 | |
539 | The "result" method, finally, just waits for the finished signal (if the |
1221 | The "result" method, finally, just waits for the finished signal (if the |
540 | request was already finished, it doesn't wait, of course, and returns |
1222 | request was already finished, it doesn't wait, of course, and returns |
541 | the data: |
1223 | the data: |
542 | |
1224 | |
543 | $txn->{finished}->wait; |
1225 | $txn->{finished}->recv; |
544 | return $txn->{result}; |
1226 | return $txn->{result}; |
545 | |
1227 | |
546 | The actual code goes further and collects all errors ("die"s, |
1228 | The actual code goes further and collects all errors ("die"s, |
547 | exceptions) that occured during request processing. The "result" method |
1229 | exceptions) that occurred during request processing. The "result" method |
548 | detects whether an exception as thrown (it is stored inside the $txn |
1230 | detects whether an exception as thrown (it is stored inside the $txn |
549 | object) and just throws the exception, which means connection errors and |
1231 | object) and just throws the exception, which means connection errors and |
550 | other problems get reported tot he code that tries to use the result, |
1232 | other problems get reported tot he code that tries to use the result, |
551 | not in a random callback. |
1233 | not in a random callback. |
552 | |
1234 | |
… | |
… | |
583 | |
1265 | |
584 | my $quit = AnyEvent->condvar; |
1266 | my $quit = AnyEvent->condvar; |
585 | |
1267 | |
586 | $fcp->txn_client_get ($url)->cb (sub { |
1268 | $fcp->txn_client_get ($url)->cb (sub { |
587 | ... |
1269 | ... |
588 | $quit->broadcast; |
1270 | $quit->send; |
589 | }); |
1271 | }); |
590 | |
1272 | |
591 | $quit->wait; |
1273 | $quit->recv; |
|
|
1274 | |
|
|
1275 | BENCHMARKS |
|
|
1276 | To give you an idea of the performance and overheads that AnyEvent adds |
|
|
1277 | over the event loops themselves and to give you an impression of the |
|
|
1278 | speed of various event loops I prepared some benchmarks. |
|
|
1279 | |
|
|
1280 | BENCHMARKING ANYEVENT OVERHEAD |
|
|
1281 | Here is a benchmark of various supported event models used natively and |
|
|
1282 | through AnyEvent. The benchmark creates a lot of timers (with a zero |
|
|
1283 | timeout) and I/O watchers (watching STDOUT, a pty, to become writable, |
|
|
1284 | which it is), lets them fire exactly once and destroys them again. |
|
|
1285 | |
|
|
1286 | Source code for this benchmark is found as eg/bench in the AnyEvent |
|
|
1287 | distribution. |
|
|
1288 | |
|
|
1289 | Explanation of the columns |
|
|
1290 | *watcher* is the number of event watchers created/destroyed. Since |
|
|
1291 | different event models feature vastly different performances, each event |
|
|
1292 | loop was given a number of watchers so that overall runtime is |
|
|
1293 | acceptable and similar between tested event loop (and keep them from |
|
|
1294 | crashing): Glib would probably take thousands of years if asked to |
|
|
1295 | process the same number of watchers as EV in this benchmark. |
|
|
1296 | |
|
|
1297 | *bytes* is the number of bytes (as measured by the resident set size, |
|
|
1298 | RSS) consumed by each watcher. This method of measuring captures both C |
|
|
1299 | and Perl-based overheads. |
|
|
1300 | |
|
|
1301 | *create* is the time, in microseconds (millionths of seconds), that it |
|
|
1302 | takes to create a single watcher. The callback is a closure shared |
|
|
1303 | between all watchers, to avoid adding memory overhead. That means |
|
|
1304 | closure creation and memory usage is not included in the figures. |
|
|
1305 | |
|
|
1306 | *invoke* is the time, in microseconds, used to invoke a simple callback. |
|
|
1307 | The callback simply counts down a Perl variable and after it was invoked |
|
|
1308 | "watcher" times, it would "->send" a condvar once to signal the end of |
|
|
1309 | this phase. |
|
|
1310 | |
|
|
1311 | *destroy* is the time, in microseconds, that it takes to destroy a |
|
|
1312 | single watcher. |
|
|
1313 | |
|
|
1314 | Results |
|
|
1315 | name watchers bytes create invoke destroy comment |
|
|
1316 | EV/EV 400000 224 0.47 0.35 0.27 EV native interface |
|
|
1317 | EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers |
|
|
1318 | CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal |
|
|
1319 | Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation |
|
|
1320 | Event/Event 16000 517 32.20 31.80 0.81 Event native interface |
|
|
1321 | Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers |
|
|
1322 | IOAsync/Any 16000 989 38.10 32.77 11.13 via IO::Async::Loop::IO_Poll |
|
|
1323 | IOAsync/Any 16000 990 37.59 29.50 10.61 via IO::Async::Loop::Epoll |
|
|
1324 | Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour |
|
|
1325 | Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers |
|
|
1326 | POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event |
|
|
1327 | POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select |
|
|
1328 | |
|
|
1329 | Discussion |
|
|
1330 | The benchmark does *not* measure scalability of the event loop very |
|
|
1331 | well. For example, a select-based event loop (such as the pure perl one) |
|
|
1332 | can never compete with an event loop that uses epoll when the number of |
|
|
1333 | file descriptors grows high. In this benchmark, all events become ready |
|
|
1334 | at the same time, so select/poll-based implementations get an unnatural |
|
|
1335 | speed boost. |
|
|
1336 | |
|
|
1337 | Also, note that the number of watchers usually has a nonlinear effect on |
|
|
1338 | overall speed, that is, creating twice as many watchers doesn't take |
|
|
1339 | twice the time - usually it takes longer. This puts event loops tested |
|
|
1340 | with a higher number of watchers at a disadvantage. |
|
|
1341 | |
|
|
1342 | To put the range of results into perspective, consider that on the |
|
|
1343 | benchmark machine, handling an event takes roughly 1600 CPU cycles with |
|
|
1344 | EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 |
|
|
1345 | CPU cycles with POE. |
|
|
1346 | |
|
|
1347 | "EV" is the sole leader regarding speed and memory use, which are both |
|
|
1348 | maximal/minimal, respectively. Even when going through AnyEvent, it uses |
|
|
1349 | far less memory than any other event loop and is still faster than Event |
|
|
1350 | natively. |
|
|
1351 | |
|
|
1352 | The pure perl implementation is hit in a few sweet spots (both the |
|
|
1353 | constant timeout and the use of a single fd hit optimisations in the |
|
|
1354 | perl interpreter and the backend itself). Nevertheless this shows that |
|
|
1355 | it adds very little overhead in itself. Like any select-based backend |
|
|
1356 | its performance becomes really bad with lots of file descriptors (and |
|
|
1357 | few of them active), of course, but this was not subject of this |
|
|
1358 | benchmark. |
|
|
1359 | |
|
|
1360 | The "Event" module has a relatively high setup and callback invocation |
|
|
1361 | cost, but overall scores in on the third place. |
|
|
1362 | |
|
|
1363 | "IO::Async" performs admirably well, about on par with "Event", even |
|
|
1364 | when using its pure perl backend. |
|
|
1365 | |
|
|
1366 | "Glib"'s memory usage is quite a bit higher, but it features a faster |
|
|
1367 | callback invocation and overall ends up in the same class as "Event". |
|
|
1368 | However, Glib scales extremely badly, doubling the number of watchers |
|
|
1369 | increases the processing time by more than a factor of four, making it |
|
|
1370 | completely unusable when using larger numbers of watchers (note that |
|
|
1371 | only a single file descriptor was used in the benchmark, so |
|
|
1372 | inefficiencies of "poll" do not account for this). |
|
|
1373 | |
|
|
1374 | The "Tk" adaptor works relatively well. The fact that it crashes with |
|
|
1375 | more than 2000 watchers is a big setback, however, as correctness takes |
|
|
1376 | precedence over speed. Nevertheless, its performance is surprising, as |
|
|
1377 | the file descriptor is dup()ed for each watcher. This shows that the |
|
|
1378 | dup() employed by some adaptors is not a big performance issue (it does |
|
|
1379 | incur a hidden memory cost inside the kernel which is not reflected in |
|
|
1380 | the figures above). |
|
|
1381 | |
|
|
1382 | "POE", regardless of underlying event loop (whether using its pure perl |
|
|
1383 | select-based backend or the Event module, the POE-EV backend couldn't be |
|
|
1384 | tested because it wasn't working) shows abysmal performance and memory |
|
|
1385 | usage with AnyEvent: Watchers use almost 30 times as much memory as EV |
|
|
1386 | watchers, and 10 times as much memory as Event (the high memory |
|
|
1387 | requirements are caused by requiring a session for each watcher). |
|
|
1388 | Watcher invocation speed is almost 900 times slower than with AnyEvent's |
|
|
1389 | pure perl implementation. |
|
|
1390 | |
|
|
1391 | The design of the POE adaptor class in AnyEvent can not really account |
|
|
1392 | for the performance issues, though, as session creation overhead is |
|
|
1393 | small compared to execution of the state machine, which is coded pretty |
|
|
1394 | optimally within AnyEvent::Impl::POE (and while everybody agrees that |
|
|
1395 | using multiple sessions is not a good approach, especially regarding |
|
|
1396 | memory usage, even the author of POE could not come up with a faster |
|
|
1397 | design). |
|
|
1398 | |
|
|
1399 | Summary |
|
|
1400 | * Using EV through AnyEvent is faster than any other event loop (even |
|
|
1401 | when used without AnyEvent), but most event loops have acceptable |
|
|
1402 | performance with or without AnyEvent. |
|
|
1403 | |
|
|
1404 | * The overhead AnyEvent adds is usually much smaller than the overhead |
|
|
1405 | of the actual event loop, only with extremely fast event loops such |
|
|
1406 | as EV adds AnyEvent significant overhead. |
|
|
1407 | |
|
|
1408 | * You should avoid POE like the plague if you want performance or |
|
|
1409 | reasonable memory usage. |
|
|
1410 | |
|
|
1411 | BENCHMARKING THE LARGE SERVER CASE |
|
|
1412 | This benchmark actually benchmarks the event loop itself. It works by |
|
|
1413 | creating a number of "servers": each server consists of a socket pair, a |
|
|
1414 | timeout watcher that gets reset on activity (but never fires), and an |
|
|
1415 | I/O watcher waiting for input on one side of the socket. Each time the |
|
|
1416 | socket watcher reads a byte it will write that byte to a random other |
|
|
1417 | "server". |
|
|
1418 | |
|
|
1419 | The effect is that there will be a lot of I/O watchers, only part of |
|
|
1420 | which are active at any one point (so there is a constant number of |
|
|
1421 | active fds for each loop iteration, but which fds these are is random). |
|
|
1422 | The timeout is reset each time something is read because that reflects |
|
|
1423 | how most timeouts work (and puts extra pressure on the event loops). |
|
|
1424 | |
|
|
1425 | In this benchmark, we use 10000 socket pairs (20000 sockets), of which |
|
|
1426 | 100 (1%) are active. This mirrors the activity of large servers with |
|
|
1427 | many connections, most of which are idle at any one point in time. |
|
|
1428 | |
|
|
1429 | Source code for this benchmark is found as eg/bench2 in the AnyEvent |
|
|
1430 | distribution. |
|
|
1431 | |
|
|
1432 | Explanation of the columns |
|
|
1433 | *sockets* is the number of sockets, and twice the number of "servers" |
|
|
1434 | (as each server has a read and write socket end). |
|
|
1435 | |
|
|
1436 | *create* is the time it takes to create a socket pair (which is |
|
|
1437 | nontrivial) and two watchers: an I/O watcher and a timeout watcher. |
|
|
1438 | |
|
|
1439 | *request*, the most important value, is the time it takes to handle a |
|
|
1440 | single "request", that is, reading the token from the pipe and |
|
|
1441 | forwarding it to another server. This includes deleting the old timeout |
|
|
1442 | and creating a new one that moves the timeout into the future. |
|
|
1443 | |
|
|
1444 | Results |
|
|
1445 | name sockets create request |
|
|
1446 | EV 20000 69.01 11.16 |
|
|
1447 | Perl 20000 73.32 35.87 |
|
|
1448 | IOAsync 20000 157.00 98.14 epoll |
|
|
1449 | IOAsync 20000 159.31 616.06 poll |
|
|
1450 | Event 20000 212.62 257.32 |
|
|
1451 | Glib 20000 651.16 1896.30 |
|
|
1452 | POE 20000 349.67 12317.24 uses POE::Loop::Event |
|
|
1453 | |
|
|
1454 | Discussion |
|
|
1455 | This benchmark *does* measure scalability and overall performance of the |
|
|
1456 | particular event loop. |
|
|
1457 | |
|
|
1458 | EV is again fastest. Since it is using epoll on my system, the setup |
|
|
1459 | time is relatively high, though. |
|
|
1460 | |
|
|
1461 | Perl surprisingly comes second. It is much faster than the C-based event |
|
|
1462 | loops Event and Glib. |
|
|
1463 | |
|
|
1464 | IO::Async performs very well when using its epoll backend, and still |
|
|
1465 | quite good compared to Glib when using its pure perl backend. |
|
|
1466 | |
|
|
1467 | Event suffers from high setup time as well (look at its code and you |
|
|
1468 | will understand why). Callback invocation also has a high overhead |
|
|
1469 | compared to the "$_->() for .."-style loop that the Perl event loop |
|
|
1470 | uses. Event uses select or poll in basically all documented |
|
|
1471 | configurations. |
|
|
1472 | |
|
|
1473 | Glib is hit hard by its quadratic behaviour w.r.t. many watchers. It |
|
|
1474 | clearly fails to perform with many filehandles or in busy servers. |
|
|
1475 | |
|
|
1476 | POE is still completely out of the picture, taking over 1000 times as |
|
|
1477 | long as EV, and over 100 times as long as the Perl implementation, even |
|
|
1478 | though it uses a C-based event loop in this case. |
|
|
1479 | |
|
|
1480 | Summary |
|
|
1481 | * The pure perl implementation performs extremely well. |
|
|
1482 | |
|
|
1483 | * Avoid Glib or POE in large projects where performance matters. |
|
|
1484 | |
|
|
1485 | BENCHMARKING SMALL SERVERS |
|
|
1486 | While event loops should scale (and select-based ones do not...) even to |
|
|
1487 | large servers, most programs we (or I :) actually write have only a few |
|
|
1488 | I/O watchers. |
|
|
1489 | |
|
|
1490 | In this benchmark, I use the same benchmark program as in the large |
|
|
1491 | server case, but it uses only eight "servers", of which three are active |
|
|
1492 | at any one time. This should reflect performance for a small server |
|
|
1493 | relatively well. |
|
|
1494 | |
|
|
1495 | The columns are identical to the previous table. |
|
|
1496 | |
|
|
1497 | Results |
|
|
1498 | name sockets create request |
|
|
1499 | EV 16 20.00 6.54 |
|
|
1500 | Perl 16 25.75 12.62 |
|
|
1501 | Event 16 81.27 35.86 |
|
|
1502 | Glib 16 32.63 15.48 |
|
|
1503 | POE 16 261.87 276.28 uses POE::Loop::Event |
|
|
1504 | |
|
|
1505 | Discussion |
|
|
1506 | The benchmark tries to test the performance of a typical small server. |
|
|
1507 | While knowing how various event loops perform is interesting, keep in |
|
|
1508 | mind that their overhead in this case is usually not as important, due |
|
|
1509 | to the small absolute number of watchers (that is, you need efficiency |
|
|
1510 | and speed most when you have lots of watchers, not when you only have a |
|
|
1511 | few of them). |
|
|
1512 | |
|
|
1513 | EV is again fastest. |
|
|
1514 | |
|
|
1515 | Perl again comes second. It is noticeably faster than the C-based event |
|
|
1516 | loops Event and Glib, although the difference is too small to really |
|
|
1517 | matter. |
|
|
1518 | |
|
|
1519 | POE also performs much better in this case, but is is still far behind |
|
|
1520 | the others. |
|
|
1521 | |
|
|
1522 | Summary |
|
|
1523 | * C-based event loops perform very well with small number of watchers, |
|
|
1524 | as the management overhead dominates. |
|
|
1525 | |
|
|
1526 | THE IO::Lambda BENCHMARK |
|
|
1527 | Recently I was told about the benchmark in the IO::Lambda manpage, which |
|
|
1528 | could be misinterpreted to make AnyEvent look bad. In fact, the |
|
|
1529 | benchmark simply compares IO::Lambda with POE, and IO::Lambda looks |
|
|
1530 | better (which shouldn't come as a surprise to anybody). As such, the |
|
|
1531 | benchmark is fine, and mostly shows that the AnyEvent backend from |
|
|
1532 | IO::Lambda isn't very optimal. But how would AnyEvent compare when used |
|
|
1533 | without the extra baggage? To explore this, I wrote the equivalent |
|
|
1534 | benchmark for AnyEvent. |
|
|
1535 | |
|
|
1536 | The benchmark itself creates an echo-server, and then, for 500 times, |
|
|
1537 | connects to the echo server, sends a line, waits for the reply, and then |
|
|
1538 | creates the next connection. This is a rather bad benchmark, as it |
|
|
1539 | doesn't test the efficiency of the framework or much non-blocking I/O, |
|
|
1540 | but it is a benchmark nevertheless. |
|
|
1541 | |
|
|
1542 | name runtime |
|
|
1543 | Lambda/select 0.330 sec |
|
|
1544 | + optimized 0.122 sec |
|
|
1545 | Lambda/AnyEvent 0.327 sec |
|
|
1546 | + optimized 0.138 sec |
|
|
1547 | Raw sockets/select 0.077 sec |
|
|
1548 | POE/select, components 0.662 sec |
|
|
1549 | POE/select, raw sockets 0.226 sec |
|
|
1550 | POE/select, optimized 0.404 sec |
|
|
1551 | |
|
|
1552 | AnyEvent/select/nb 0.085 sec |
|
|
1553 | AnyEvent/EV/nb 0.068 sec |
|
|
1554 | +state machine 0.134 sec |
|
|
1555 | |
|
|
1556 | The benchmark is also a bit unfair (my fault): the IO::Lambda/POE |
|
|
1557 | benchmarks actually make blocking connects and use 100% blocking I/O, |
|
|
1558 | defeating the purpose of an event-based solution. All of the newly |
|
|
1559 | written AnyEvent benchmarks use 100% non-blocking connects (using |
|
|
1560 | AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS |
|
|
1561 | resolver), so AnyEvent is at a disadvantage here, as non-blocking |
|
|
1562 | connects generally require a lot more bookkeeping and event handling |
|
|
1563 | than blocking connects (which involve a single syscall only). |
|
|
1564 | |
|
|
1565 | The last AnyEvent benchmark additionally uses AnyEvent::Handle, which |
|
|
1566 | offers similar expressive power as POE and IO::Lambda, using |
|
|
1567 | conventional Perl syntax. This means that both the echo server and the |
|
|
1568 | client are 100% non-blocking, further placing it at a disadvantage. |
|
|
1569 | |
|
|
1570 | As you can see, the AnyEvent + EV combination even beats the |
|
|
1571 | hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl |
|
|
1572 | backend easily beats IO::Lambda and POE. |
|
|
1573 | |
|
|
1574 | And even the 100% non-blocking version written using the high-level (and |
|
|
1575 | slow :) AnyEvent::Handle abstraction beats both POE and IO::Lambda by a |
|
|
1576 | large margin, even though it does all of DNS, tcp-connect and socket I/O |
|
|
1577 | in a non-blocking way. |
|
|
1578 | |
|
|
1579 | The two AnyEvent benchmarks programs can be found as eg/ae0.pl and |
|
|
1580 | eg/ae2.pl in the AnyEvent distribution, the remaining benchmarks are |
|
|
1581 | part of the IO::lambda distribution and were used without any changes. |
|
|
1582 | |
|
|
1583 | SIGNALS |
|
|
1584 | AnyEvent currently installs handlers for these signals: |
|
|
1585 | |
|
|
1586 | SIGCHLD |
|
|
1587 | A handler for "SIGCHLD" is installed by AnyEvent's child watcher |
|
|
1588 | emulation for event loops that do not support them natively. Also, |
|
|
1589 | some event loops install a similar handler. |
|
|
1590 | |
|
|
1591 | Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, |
|
|
1592 | then AnyEvent will reset it to default, to avoid losing child exit |
|
|
1593 | statuses. |
|
|
1594 | |
|
|
1595 | SIGPIPE |
|
|
1596 | A no-op handler is installed for "SIGPIPE" when $SIG{PIPE} is |
|
|
1597 | "undef" when AnyEvent gets loaded. |
|
|
1598 | |
|
|
1599 | The rationale for this is that AnyEvent users usually do not really |
|
|
1600 | depend on SIGPIPE delivery (which is purely an optimisation for |
|
|
1601 | shell use, or badly-written programs), but "SIGPIPE" can cause |
|
|
1602 | spurious and rare program exits as a lot of people do not expect |
|
|
1603 | "SIGPIPE" when writing to some random socket. |
|
|
1604 | |
|
|
1605 | The rationale for installing a no-op handler as opposed to ignoring |
|
|
1606 | it is that this way, the handler will be restored to defaults on |
|
|
1607 | exec. |
|
|
1608 | |
|
|
1609 | Feel free to install your own handler, or reset it to defaults. |
|
|
1610 | |
|
|
1611 | FORK |
|
|
1612 | Most event libraries are not fork-safe. The ones who are usually are |
|
|
1613 | because they rely on inefficient but fork-safe "select" or "poll" calls. |
|
|
1614 | Only EV is fully fork-aware. |
|
|
1615 | |
|
|
1616 | If you have to fork, you must either do so *before* creating your first |
|
|
1617 | watcher OR you must not use AnyEvent at all in the child. |
|
|
1618 | |
|
|
1619 | SECURITY CONSIDERATIONS |
|
|
1620 | AnyEvent can be forced to load any event model via |
|
|
1621 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used |
|
|
1622 | to execute arbitrary code or directly gain access, it can easily be used |
|
|
1623 | to make the program hang or malfunction in subtle ways, as AnyEvent |
|
|
1624 | watchers will not be active when the program uses a different event |
|
|
1625 | model than specified in the variable. |
|
|
1626 | |
|
|
1627 | You can make AnyEvent completely ignore this variable by deleting it |
|
|
1628 | before the first watcher gets created, e.g. with a "BEGIN" block: |
|
|
1629 | |
|
|
1630 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
|
|
1631 | |
|
|
1632 | use AnyEvent; |
|
|
1633 | |
|
|
1634 | Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can |
|
|
1635 | be used to probe what backend is used and gain other information (which |
|
|
1636 | is probably even less useful to an attacker than PERL_ANYEVENT_MODEL), |
|
|
1637 | and $ENV{PERL_ANYEVENT_STRICT}. |
|
|
1638 | |
|
|
1639 | Note that AnyEvent will remove *all* environment variables starting with |
|
|
1640 | "PERL_ANYEVENT_" from %ENV when it is loaded while taint mode is |
|
|
1641 | enabled. |
|
|
1642 | |
|
|
1643 | BUGS |
|
|
1644 | Perl 5.8 has numerous memleaks that sometimes hit this module and are |
|
|
1645 | hard to work around. If you suffer from memleaks, first upgrade to Perl |
|
|
1646 | 5.10 and check wether the leaks still show up. (Perl 5.10.0 has other |
|
|
1647 | annoying memleaks, such as leaking on "map" and "grep" but it is usually |
|
|
1648 | not as pronounced). |
592 | |
1649 | |
593 | SEE ALSO |
1650 | SEE ALSO |
594 | Event modules: Coro::EV, EV, EV::Glib, Glib::EV, Coro::Event, Event, |
1651 | Utility functions: AnyEvent::Util. |
595 | Glib::Event, Glib, Coro, Tk. |
|
|
596 | |
1652 | |
597 | Implementations: AnyEvent::Impl::CoroEV, AnyEvent::Impl::EV, |
1653 | Event modules: EV, EV::Glib, Glib::EV, Event, Glib::Event, Glib, Tk, |
598 | AnyEvent::Impl::CoroEvent, AnyEvent::Impl::Event, AnyEvent::Impl::Glib, |
1654 | Event::Lib, Qt, POE. |
|
|
1655 | |
|
|
1656 | Implementations: AnyEvent::Impl::EV, AnyEvent::Impl::Event, |
599 | AnyEvent::Impl::Tk, AnyEvent::Impl::Perl. |
1657 | AnyEvent::Impl::Glib, AnyEvent::Impl::Tk, AnyEvent::Impl::Perl, |
|
|
1658 | AnyEvent::Impl::EventLib, AnyEvent::Impl::Qt, AnyEvent::Impl::POE, |
|
|
1659 | AnyEvent::Impl::IOAsync. |
600 | |
1660 | |
|
|
1661 | Non-blocking file handles, sockets, TCP clients and servers: |
|
|
1662 | AnyEvent::Handle, AnyEvent::Socket, AnyEvent::TLS. |
|
|
1663 | |
|
|
1664 | Asynchronous DNS: AnyEvent::DNS. |
|
|
1665 | |
|
|
1666 | Coroutine support: Coro, Coro::AnyEvent, Coro::EV, Coro::Event, |
|
|
1667 | |
601 | Nontrivial usage examples: Net::FCP, Net::XMPP2. |
1668 | Nontrivial usage examples: AnyEvent::GPSD, AnyEvent::XMPP, |
|
|
1669 | AnyEvent::HTTP. |
602 | |
1670 | |
603 | AUTHOR |
1671 | AUTHOR |
604 | Marc Lehmann <schmorp@schmorp.de> |
1672 | Marc Lehmann <schmorp@schmorp.de> |
605 | http://home.schmorp.de/ |
1673 | http://home.schmorp.de/ |
606 | |
1674 | |