… | |
… | |
2 | |
2 | |
3 | EV - perl interface to libev, a high performance full-featured event loop |
3 | EV - perl interface to libev, a high performance full-featured event loop |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use EV; |
7 | use EV; |
|
|
8 | |
|
|
9 | # TIMERS |
|
|
10 | |
|
|
11 | my $w = EV::timer 2, 0, sub { |
|
|
12 | warn "is called after 2s"; |
|
|
13 | }; |
|
|
14 | |
|
|
15 | my $w = EV::timer 2, 2, sub { |
|
|
16 | warn "is called roughly every 2s (repeat = 2)"; |
|
|
17 | }; |
|
|
18 | |
|
|
19 | undef $w; # destroy event watcher again |
|
|
20 | |
|
|
21 | my $w = EV::periodic 0, 60, 0, sub { |
|
|
22 | warn "is called every minute, on the minute, exactly"; |
|
|
23 | }; |
|
|
24 | |
|
|
25 | # IO |
|
|
26 | |
|
|
27 | my $w = EV::io *STDIN, EV::READ, sub { |
|
|
28 | my ($w, $revents) = @_; # all callbacks receive the watcher and event mask |
|
|
29 | warn "stdin is readable, you entered: ", <STDIN>; |
|
|
30 | }; |
|
|
31 | |
|
|
32 | # SIGNALS |
|
|
33 | |
|
|
34 | my $w = EV::signal 'QUIT', sub { |
|
|
35 | warn "sigquit received\n"; |
|
|
36 | }; |
|
|
37 | |
|
|
38 | # CHILD/PID STATUS CHANGES |
8 | |
39 | |
9 | # TIMERS |
40 | my $w = EV::child 666, 0, sub { |
|
|
41 | my ($w, $revents) = @_; |
|
|
42 | my $status = $w->rstatus; |
|
|
43 | }; |
10 | |
44 | |
11 | my $w = EV::timer 2, 0, sub { |
|
|
12 | warn "is called after 2s"; |
|
|
13 | }; |
|
|
14 | |
|
|
15 | my $w = EV::timer 2, 2, sub { |
|
|
16 | warn "is called roughly every 2s (repeat = 2)"; |
|
|
17 | }; |
|
|
18 | |
|
|
19 | undef $w; # destroy event watcher again |
|
|
20 | |
|
|
21 | my $w = EV::periodic 0, 60, 0, sub { |
|
|
22 | warn "is called every minute, on the minute, exactly"; |
|
|
23 | }; |
|
|
24 | |
|
|
25 | # IO |
|
|
26 | |
|
|
27 | my $w = EV::io *STDIN, EV::READ, sub { |
|
|
28 | my ($w, $revents) = @_; # all callbacks receive the watcher and event mask |
|
|
29 | warn "stdin is readable, you entered: ", <STDIN>; |
|
|
30 | }; |
|
|
31 | |
|
|
32 | # SIGNALS |
|
|
33 | |
|
|
34 | my $w = EV::signal 'QUIT', sub { |
|
|
35 | warn "sigquit received\n"; |
|
|
36 | }; |
|
|
37 | |
|
|
38 | # CHILD/PID STATUS CHANGES |
|
|
39 | |
|
|
40 | my $w = EV::child 666, 0, sub { |
|
|
41 | my ($w, $revents) = @_; |
|
|
42 | my $status = $w->rstatus; |
|
|
43 | }; |
|
|
44 | |
|
|
45 | # STAT CHANGES |
45 | # STAT CHANGES |
46 | my $w = EV::stat "/etc/passwd", 10, sub { |
46 | my $w = EV::stat "/etc/passwd", 10, sub { |
47 | my ($w, $revents) = @_; |
47 | my ($w, $revents) = @_; |
48 | warn $w->path, " has changed somehow.\n"; |
48 | warn $w->path, " has changed somehow.\n"; |
49 | }; |
49 | }; |
50 | |
50 | |
51 | # MAINLOOP |
51 | # MAINLOOP |
52 | EV::loop; # loop until EV::unloop is called or all watchers stop |
52 | EV::loop; # loop until EV::unloop is called or all watchers stop |
53 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
53 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
54 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
54 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
|
|
55 | |
|
|
56 | =head1 BEFORE YOU START USING THIS MODULE |
|
|
57 | |
|
|
58 | If you only need timer, I/O, signal, child and idle watchers and not the |
|
|
59 | advanced functionality of this module, consider using L<AnyEvent> instead, |
|
|
60 | specifically the simplified API described in L<AE>. |
|
|
61 | |
|
|
62 | When used with EV as backend, the L<AE> API is as fast as the native L<EV> |
|
|
63 | API, but your programs/modules will still run with many other event loops. |
55 | |
64 | |
56 | =head1 DESCRIPTION |
65 | =head1 DESCRIPTION |
57 | |
66 | |
58 | This module provides an interface to libev |
67 | This module provides an interface to libev |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
68 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
60 | below is comprehensive, one might also consult the documentation of libev |
69 | below is comprehensive, one might also consult the documentation of |
61 | itself (L<http://cvs.schmorp.de/libev/ev.html>) for more subtle details on |
70 | libev itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod> or |
62 | watcher semantics or some discussion on the available backends, or how to |
71 | F<perldoc EV::libev>) for more subtle details on watcher semantics or some |
63 | force a specific backend with C<LIBEV_FLAGS>, or just about in any case |
72 | discussion on the available backends, or how to force a specific backend |
64 | because it has much more detailed information. |
73 | with C<LIBEV_FLAGS>, or just about in any case because it has much more |
|
|
74 | detailed information. |
|
|
75 | |
|
|
76 | This module is very fast and scalable. It is actually so fast that you |
|
|
77 | can use it through the L<AnyEvent> module, stay portable to other event |
|
|
78 | loops (if you don't rely on any watcher types not available through it) |
|
|
79 | and still be faster than with any other event loop currently supported in |
|
|
80 | Perl. |
|
|
81 | |
|
|
82 | =head2 PORTING FROM EV 3.X to 4.X |
|
|
83 | |
|
|
84 | EV version 4 introduces a number of incompatible changes summarised |
|
|
85 | here. According to the depreciation strategy used by libev, there is a |
|
|
86 | compatibility layer in place so programs should continue to run unchanged |
|
|
87 | (the XS interface lacks this layer, so programs using that one need to be |
|
|
88 | updated). |
|
|
89 | |
|
|
90 | This compatibility layer will be switched off in some future release. |
|
|
91 | |
|
|
92 | All changes relevant to Perl are renames of symbols, functions and |
|
|
93 | methods: |
|
|
94 | |
|
|
95 | EV::loop => EV::run |
|
|
96 | EV::LOOP_NONBLOCK => EV::RUN_NOWAIT |
|
|
97 | EV::LOOP_ONESHOT => EV::RUN_ONCE |
|
|
98 | |
|
|
99 | EV::unloop => EV::break |
|
|
100 | EV::UNLOOP_CANCEL => EV::BREAK_CANCEL |
|
|
101 | EV::UNLOOP_ONE => EV::BREAK_ONE |
|
|
102 | EV::UNLOOP_ALL => EV::BREAK_ALL |
|
|
103 | |
|
|
104 | EV::TIMEOUT => EV::TIMER |
|
|
105 | |
|
|
106 | EV::loop_count => EV::iteration |
|
|
107 | EV::loop_depth => EV::depth |
|
|
108 | EV::loop_verify => EV::verify |
|
|
109 | |
|
|
110 | The loop object methods corresponding to the functions above have been |
|
|
111 | similarly renamed. |
|
|
112 | |
|
|
113 | =head2 MODULE EXPORTS |
|
|
114 | |
|
|
115 | This module does not export any symbols. |
65 | |
116 | |
66 | =cut |
117 | =cut |
67 | |
118 | |
68 | package EV; |
119 | package EV; |
69 | |
120 | |
70 | use strict; |
121 | use common::sense; |
71 | |
122 | |
72 | BEGIN { |
123 | BEGIN { |
73 | our $VERSION = '3.0'; |
124 | our $VERSION = '4.01'; |
74 | use XSLoader; |
125 | use XSLoader; |
75 | XSLoader::load "EV", $VERSION; |
126 | XSLoader::load "EV", $VERSION; |
76 | } |
127 | } |
77 | |
128 | |
78 | @EV::IO::ISA = |
129 | @EV::IO::ISA = |
… | |
… | |
84 | @EV::Idle::ISA = |
135 | @EV::Idle::ISA = |
85 | @EV::Prepare::ISA = |
136 | @EV::Prepare::ISA = |
86 | @EV::Check::ISA = |
137 | @EV::Check::ISA = |
87 | @EV::Embed::ISA = |
138 | @EV::Embed::ISA = |
88 | @EV::Fork::ISA = |
139 | @EV::Fork::ISA = |
|
|
140 | @EV::Async::ISA = |
89 | "EV::Watcher"; |
141 | "EV::Watcher"; |
90 | |
142 | |
91 | @EV::Loop::Default::ISA = "EV::Loop"; |
143 | @EV::Loop::Default::ISA = "EV::Loop"; |
92 | |
144 | |
93 | =head1 EVENT LOOPS |
145 | =head1 EVENT LOOPS |
… | |
… | |
104 | default loop as this is fastest (perl-wise), best supported by other |
156 | default loop as this is fastest (perl-wise), best supported by other |
105 | modules (e.g. AnyEvent or Coro) and most portable event loop. |
157 | modules (e.g. AnyEvent or Coro) and most portable event loop. |
106 | |
158 | |
107 | For specific programs you can create additional event loops dynamically. |
159 | For specific programs you can create additional event loops dynamically. |
108 | |
160 | |
109 | =over 4 |
161 | If you want to take advantage of kqueue (which often works properly for |
|
|
162 | sockets only) even though the default loop doesn't enable it, you can |
|
|
163 | I<embed> a kqueue loop into the default loop: running the default loop |
|
|
164 | will then also service the kqueue loop to some extent. See the example in |
|
|
165 | the section about embed watchers for an example on how to achieve that. |
110 | |
166 | |
|
|
167 | =over 4 |
|
|
168 | |
111 | =item $loop = new EV::loop [$flags] |
169 | =item $loop = new EV::Loop [$flags] |
112 | |
170 | |
113 | Create a new event loop as per the specified flags. Please refer to the |
171 | Create a new event loop as per the specified flags. Please refer to |
114 | C<ev_loop_new ()> function description in the libev documentation |
172 | the C<ev_loop_new ()> function description in the libev documentation |
115 | (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>) |
173 | (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>, |
116 | for more info. |
174 | or locally-installed as F<EV::libev> manpage) for more info. |
117 | |
175 | |
118 | The loop will automatically be destroyed when it is no longer referenced |
176 | The loop will automatically be destroyed when it is no longer referenced |
119 | by any watcher and the loop object goes out of scope. |
177 | by any watcher and the loop object goes out of scope. |
120 | |
178 | |
121 | Using C<EV::FLAG_FORKCHECK> is recommended, as only the default event loop |
179 | If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK> |
122 | is protected by this module. |
180 | is recommended, as only the default event loop is protected by this |
|
|
181 | module. If you I<are> embedding this loop in the default loop, this is not |
|
|
182 | necessary, as C<EV::embed> automatically does the right thing on fork. |
123 | |
183 | |
124 | =item $loop->loop_fork |
184 | =item $loop->loop_fork |
125 | |
185 | |
126 | Must be called after a fork in the child, before entering or continuing |
186 | Must be called after a fork in the child, before entering or continuing |
127 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
187 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
128 | this fucntion automatically, at some performance loss (refer to the libev |
188 | this function automatically, at some performance loss (refer to the libev |
129 | documentation). |
189 | documentation). |
130 | |
190 | |
|
|
191 | =item $loop->loop_verify |
|
|
192 | |
|
|
193 | Calls C<ev_verify> to make internal consistency checks (for debugging |
|
|
194 | libev) and abort the program if any data structures were found to be |
|
|
195 | corrupted. |
|
|
196 | |
131 | =item $loop = EV::default_loop [$flags] |
197 | =item $loop = EV::default_loop [$flags] |
132 | |
198 | |
133 | Return the default loop (which is a singleton object). |
199 | Return the default loop (which is a singleton object). Since this module |
|
|
200 | already creates the default loop with default flags, specifying flags here |
|
|
201 | will not have any effect unless you destroy the default loop first, which |
|
|
202 | isn't supported. So in short: don't do it, and if you break it, you get to |
|
|
203 | keep the pieces. |
134 | |
204 | |
135 | =back |
205 | =back |
136 | |
206 | |
137 | |
207 | |
138 | =head1 BASIC INTERFACE |
208 | =head1 BASIC INTERFACE |
… | |
… | |
168 | =item $time = EV::now |
238 | =item $time = EV::now |
169 | |
239 | |
170 | =item $time = $loop->now |
240 | =item $time = $loop->now |
171 | |
241 | |
172 | Returns the time the last event loop iteration has been started. This |
242 | Returns the time the last event loop iteration has been started. This |
173 | is the time that (relative) timers are based on, and refering to it is |
243 | is the time that (relative) timers are based on, and referring to it is |
174 | usually faster then calling EV::time. |
244 | usually faster then calling EV::time. |
175 | |
245 | |
|
|
246 | =item EV::now_update |
|
|
247 | |
|
|
248 | =item $loop->now_update |
|
|
249 | |
|
|
250 | Establishes the current time by querying the kernel, updating the time |
|
|
251 | returned by C<EV::now> in the progress. This is a costly operation and |
|
|
252 | is usually done automatically within C<EV::loop>. |
|
|
253 | |
|
|
254 | This function is rarely useful, but when some event callback runs for a |
|
|
255 | very long time without entering the event loop, updating libev's idea of |
|
|
256 | the current time is a good idea. |
|
|
257 | |
|
|
258 | =item EV::suspend |
|
|
259 | |
|
|
260 | =item $loop->suspend |
|
|
261 | |
|
|
262 | =item EV::resume |
|
|
263 | |
|
|
264 | =item $loop->resume |
|
|
265 | |
|
|
266 | These two functions suspend and resume a loop, for use when the loop is |
|
|
267 | not used for a while and timeouts should not be processed. |
|
|
268 | |
|
|
269 | A typical use case would be an interactive program such as a game: When |
|
|
270 | the user presses C<^Z> to suspend the game and resumes it an hour later it |
|
|
271 | would be best to handle timeouts as if no time had actually passed while |
|
|
272 | the program was suspended. This can be achieved by calling C<suspend> |
|
|
273 | in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling |
|
|
274 | C<resume> directly afterwards to resume timer processing. |
|
|
275 | |
|
|
276 | Effectively, all C<timer> watchers will be delayed by the time spend |
|
|
277 | between C<suspend> and C<resume>, and all C<periodic> watchers |
|
|
278 | will be rescheduled (that is, they will lose any events that would have |
|
|
279 | occured while suspended). |
|
|
280 | |
|
|
281 | After calling C<suspend> you B<must not> call I<any> function on the given |
|
|
282 | loop other than C<resume>, and you B<must not> call C<resume> |
|
|
283 | without a previous call to C<suspend>. |
|
|
284 | |
|
|
285 | Calling C<suspend>/C<resume> has the side effect of updating the event |
|
|
286 | loop time (see C<now_update>). |
|
|
287 | |
176 | =item $backend = EV::backend |
288 | =item $backend = EV::backend |
177 | |
289 | |
178 | =item $backend = $loop->backend |
290 | =item $backend = $loop->backend |
179 | |
291 | |
180 | Returns an integer describing the backend used by libev (EV::METHOD_SELECT |
292 | Returns an integer describing the backend used by libev (EV::BACKEND_SELECT |
181 | or EV::METHOD_EPOLL). |
293 | or EV::BACKEND_EPOLL). |
182 | |
294 | |
183 | =item EV::loop [$flags] |
295 | =item EV::loop [$flags] |
184 | |
296 | |
185 | =item $loop->loop ([$flags]) |
297 | =item $loop->loop ([$flags]) |
186 | |
298 | |
… | |
… | |
206 | =item $count = EV::loop_count |
318 | =item $count = EV::loop_count |
207 | |
319 | |
208 | =item $count = $loop->loop_count |
320 | =item $count = $loop->loop_count |
209 | |
321 | |
210 | Return the number of times the event loop has polled for new |
322 | Return the number of times the event loop has polled for new |
211 | events. Sometiems useful as a generation counter. |
323 | events. Sometimes useful as a generation counter. |
212 | |
324 | |
213 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
325 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
214 | |
326 | |
215 | =item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) |
327 | =item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) |
216 | |
328 | |
… | |
… | |
227 | timeout. Otherwise a EV::timer with this value will be started. |
339 | timeout. Otherwise a EV::timer with this value will be started. |
228 | |
340 | |
229 | When an error occurs or either the timeout or I/O watcher triggers, then |
341 | When an error occurs or either the timeout or I/O watcher triggers, then |
230 | the callback will be called with the received event set (in general |
342 | the callback will be called with the received event set (in general |
231 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
343 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
232 | C<EV::WRITE> and C<EV::TIMEOUT>). |
344 | C<EV::WRITE> and C<EV::TIMER>). |
233 | |
345 | |
234 | EV::once doesn't return anything: the watchers stay active till either |
346 | EV::once doesn't return anything: the watchers stay active till either |
235 | of them triggers, then they will be stopped and freed, and the callback |
347 | of them triggers, then they will be stopped and freed, and the callback |
236 | invoked. |
348 | invoked. |
237 | |
349 | |
… | |
… | |
256 | |
368 | |
257 | =item $loop->set_timeout_collect_interval ($time) |
369 | =item $loop->set_timeout_collect_interval ($time) |
258 | |
370 | |
259 | These advanced functions set the minimum block interval when polling for I/O events and the minimum |
371 | These advanced functions set the minimum block interval when polling for I/O events and the minimum |
260 | wait interval for timer events. See the libev documentation at |
372 | wait interval for timer events. See the libev documentation at |
261 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> for |
373 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> |
262 | a more detailed discussion. |
374 | (locally installed as F<EV::libev>) for a more detailed discussion. |
|
|
375 | |
|
|
376 | =item $count = EV::pending_count |
|
|
377 | |
|
|
378 | =item $count = $loop->pending_count |
|
|
379 | |
|
|
380 | Returns the number of currently pending watchers. |
|
|
381 | |
|
|
382 | =item EV::invoke_pending |
|
|
383 | |
|
|
384 | =item $loop->invoke_pending |
|
|
385 | |
|
|
386 | Invoke all currently pending watchers. |
263 | |
387 | |
264 | =back |
388 | =back |
265 | |
389 | |
266 | |
390 | |
267 | =head1 WATCHER OBJECTS |
391 | =head1 WATCHER OBJECTS |
268 | |
392 | |
269 | A watcher is an object that gets created to record your interest in some |
393 | A watcher is an object that gets created to record your interest in some |
270 | event. For instance, if you want to wait for STDIN to become readable, you |
394 | event. For instance, if you want to wait for STDIN to become readable, you |
271 | would create an EV::io watcher for that: |
395 | would create an EV::io watcher for that: |
272 | |
396 | |
273 | my $watcher = EV::io *STDIN, EV::READ, sub { |
397 | my $watcher = EV::io *STDIN, EV::READ, sub { |
274 | my ($watcher, $revents) = @_; |
398 | my ($watcher, $revents) = @_; |
275 | warn "yeah, STDIN should now be readable without blocking!\n" |
399 | warn "yeah, STDIN should now be readable without blocking!\n" |
276 | }; |
400 | }; |
277 | |
401 | |
278 | All watchers can be active (waiting for events) or inactive (paused). Only |
402 | All watchers can be active (waiting for events) or inactive (paused). Only |
279 | active watchers will have their callbacks invoked. All callbacks will be |
403 | active watchers will have their callbacks invoked. All callbacks will be |
280 | called with at least two arguments: the watcher and a bitmask of received |
404 | called with at least two arguments: the watcher and a bitmask of received |
281 | events. |
405 | events. |
282 | |
406 | |
283 | Each watcher type has its associated bit in revents, so you can use the |
407 | Each watcher type has its associated bit in revents, so you can use the |
284 | same callback for multiple watchers. The event mask is named after the |
408 | same callback for multiple watchers. The event mask is named after the |
285 | type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
409 | type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
286 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
410 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
287 | (which can set both EV::READ and EV::WRITE bits), and EV::timer (which |
411 | (which can set both EV::READ and EV::WRITE bits). |
288 | uses EV::TIMEOUT). |
|
|
289 | |
412 | |
290 | In the rare case where one wants to create a watcher but not start it at |
413 | In the rare case where one wants to create a watcher but not start it at |
291 | the same time, each constructor has a variant with a trailing C<_ns> in |
414 | the same time, each constructor has a variant with a trailing C<_ns> in |
292 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
415 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
293 | |
416 | |
… | |
… | |
372 | |
495 | |
373 | =item $previous_state = $w->keepalive ($bool) |
496 | =item $previous_state = $w->keepalive ($bool) |
374 | |
497 | |
375 | Normally, C<EV::loop> will return when there are no active watchers |
498 | Normally, C<EV::loop> will return when there are no active watchers |
376 | (which is a "deadlock" because no progress can be made anymore). This is |
499 | (which is a "deadlock" because no progress can be made anymore). This is |
377 | convinient because it allows you to start your watchers (and your jobs), |
500 | convenient because it allows you to start your watchers (and your jobs), |
378 | call C<EV::loop> once and when it returns you know that all your jobs are |
501 | call C<EV::loop> once and when it returns you know that all your jobs are |
379 | finished (or they forgot to register some watchers for their task :). |
502 | finished (or they forgot to register some watchers for their task :). |
380 | |
503 | |
381 | Sometimes, however, this gets in your way, for example when the module |
504 | Sometimes, however, this gets in your way, for example when the module |
382 | that calls C<EV::loop> (usually the main program) is not the same module |
505 | that calls C<EV::loop> (usually the main program) is not the same module |
… | |
… | |
386 | because you happen to have this long-running UDP port watcher. |
509 | because you happen to have this long-running UDP port watcher. |
387 | |
510 | |
388 | In this case you can clear the keepalive status, which means that even |
511 | In this case you can clear the keepalive status, which means that even |
389 | though your watcher is active, it won't keep C<EV::loop> from returning. |
512 | though your watcher is active, it won't keep C<EV::loop> from returning. |
390 | |
513 | |
391 | The initial value for keepalive is true (enabled), and you cna change it |
514 | The initial value for keepalive is true (enabled), and you can change it |
392 | any time. |
515 | any time. |
393 | |
516 | |
394 | Example: Register an I/O watcher for some UDP socket but do not keep the |
517 | Example: Register an I/O watcher for some UDP socket but do not keep the |
395 | event loop from running just because of that watcher. |
518 | event loop from running just because of that watcher. |
396 | |
519 | |
397 | my $udp_socket = ... |
520 | my $udp_socket = ... |
398 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
521 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
399 | $1000udp_watcher->keepalive (0); |
522 | $udp_watcher->keepalive (0); |
400 | |
523 | |
401 | =item $loop = $w->loop |
524 | =item $loop = $w->loop |
402 | |
525 | |
403 | Return the loop that this watcher is attached to. |
526 | Return the loop that this watcher is attached to. |
404 | |
527 | |
… | |
… | |
533 | This time simply fires at the wallclock time C<$at> and doesn't repeat. It |
656 | This time simply fires at the wallclock time C<$at> and doesn't repeat. It |
534 | will not adjust when a time jump occurs, that is, if it is to be run |
657 | will not adjust when a time jump occurs, that is, if it is to be run |
535 | at January 1st 2011 then it will run when the system time reaches or |
658 | at January 1st 2011 then it will run when the system time reaches or |
536 | surpasses this time. |
659 | surpasses this time. |
537 | |
660 | |
538 | =item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0) |
661 | =item * repeating interval timer ($interval > 0, $reschedule_cb = 0) |
539 | |
662 | |
540 | In this mode the watcher will always be scheduled to time out at the |
663 | In this mode the watcher will always be scheduled to time out at the |
541 | next C<$at + N * $interval> time (for some integer N) and then repeat, |
664 | next C<$at + N * $interval> time (for some integer N) and then repeat, |
542 | regardless of any time jumps. |
665 | regardless of any time jumps. |
543 | |
666 | |
… | |
… | |
561 | time the periodic watcher gets scheduled, the reschedule callback |
684 | time the periodic watcher gets scheduled, the reschedule callback |
562 | ($reschedule_cb) will be called with the watcher as first, and the current |
685 | ($reschedule_cb) will be called with the watcher as first, and the current |
563 | time as second argument. |
686 | time as second argument. |
564 | |
687 | |
565 | I<This callback MUST NOT stop or destroy this or any other periodic |
688 | I<This callback MUST NOT stop or destroy this or any other periodic |
566 | watcher, ever>. If you need to stop it, return 1e30 and stop it |
689 | watcher, ever, and MUST NOT call any event loop functions or methods>. If |
567 | afterwards. |
690 | you need to stop it, return 1e30 and stop it afterwards. You may create |
|
|
691 | and start a C<EV::prepare> watcher for this task. |
568 | |
692 | |
569 | It must return the next time to trigger, based on the passed time value |
693 | It must return the next time to trigger, based on the passed time value |
570 | (that is, the lowest time value larger than to the second argument). It |
694 | (that is, the lowest time value larger than or equal to to the second |
571 | will usually be called just before the callback will be triggered, but |
695 | argument). It will usually be called just before the callback will be |
572 | might be called at other times, too. |
696 | triggered, but might be called at other times, too. |
573 | |
697 | |
574 | This can be used to create very complex timers, such as a timer that |
698 | This can be used to create very complex timers, such as a timer that |
575 | triggers on each midnight, local time (actually 24 hours after the last |
699 | triggers on each midnight, local time (actually 24 hours after the last |
576 | midnight, to keep the example simple. If you know a way to do it correctly |
700 | midnight, to keep the example simple. If you know a way to do it correctly |
577 | in about the same space (without requiring elaborate modules), drop me a |
701 | in about the same space (without requiring elaborate modules), drop me a |
… | |
… | |
613 | |
737 | |
614 | =item $w = EV::signal $signal, $callback |
738 | =item $w = EV::signal $signal, $callback |
615 | |
739 | |
616 | =item $w = EV::signal_ns $signal, $callback |
740 | =item $w = EV::signal_ns $signal, $callback |
617 | |
741 | |
|
|
742 | =item $w = $loop->signal ($signal, $callback) |
|
|
743 | |
|
|
744 | =item $w = $loop->signal_ns ($signal, $callback) |
|
|
745 | |
618 | Call the callback when $signal is received (the signal can be specified by |
746 | Call the callback when $signal is received (the signal can be specified by |
619 | number or by name, just as with C<kill> or C<%SIG>). |
747 | number or by name, just as with C<kill> or C<%SIG>). |
|
|
748 | |
|
|
749 | Only one event loop can grab a given signal - attempting to grab the same |
|
|
750 | signal from two EV loops will crash the program immediately or cause data |
|
|
751 | corruption. |
620 | |
752 | |
621 | EV will grab the signal for the process (the kernel only allows one |
753 | EV will grab the signal for the process (the kernel only allows one |
622 | component to receive a signal at a time) when you start a signal watcher, |
754 | component to receive a signal at a time) when you start a signal watcher, |
623 | and removes it again when you stop it. Perl does the same when you |
755 | and removes it again when you stop it. Perl does the same when you |
624 | add/remove callbacks to C<%SIG>, so watch out. |
756 | add/remove callbacks to C<%SIG>, so watch out. |
… | |
… | |
849 | =item $w = $loop->check_ns ($callback) |
981 | =item $w = $loop->check_ns ($callback) |
850 | |
982 | |
851 | Call the callback just after the process wakes up again (after it has |
983 | Call the callback just after the process wakes up again (after it has |
852 | gathered events), but before any other callbacks have been invoked. |
984 | gathered events), but before any other callbacks have been invoked. |
853 | |
985 | |
854 | This is used to integrate other event-based software into the EV |
986 | This can be used to integrate other event-based software into the EV |
855 | mainloop: You register a prepare callback and in there, you create io and |
987 | mainloop: You register a prepare callback and in there, you create io and |
856 | timer watchers as required by the other software. Here is a real-world |
988 | timer watchers as required by the other software. Here is a real-world |
857 | example of integrating Net::SNMP (with some details left out): |
989 | example of integrating Net::SNMP (with some details left out): |
858 | |
990 | |
859 | our @snmp_watcher; |
991 | our @snmp_watcher; |
… | |
… | |
889 | # make the dispatcher handle any new stuff |
1021 | # make the dispatcher handle any new stuff |
890 | ... not shown |
1022 | ... not shown |
891 | }; |
1023 | }; |
892 | |
1024 | |
893 | The callbacks of the created watchers will not be called as the watchers |
1025 | The callbacks of the created watchers will not be called as the watchers |
894 | are destroyed before this cna happen (remember EV::check gets called |
1026 | are destroyed before this can happen (remember EV::check gets called |
895 | first). |
1027 | first). |
896 | |
1028 | |
897 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
1029 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
|
|
1030 | |
|
|
1031 | =item EV::CHECK constant issues |
|
|
1032 | |
|
|
1033 | Like all other watcher types, there is a bitmask constant for use in |
|
|
1034 | C<$revents> and other places. The C<EV::CHECK> is special as it has |
|
|
1035 | the same name as the C<CHECK> sub called by Perl. This doesn't cause |
|
|
1036 | big issues on newer perls (beginning with 5.8.9), but it means thatthe |
|
|
1037 | constant must be I<inlined>, i.e. runtime calls will not work. That means |
|
|
1038 | that as long as you always C<use EV> and then C<EV::CHECK> you are on the |
|
|
1039 | safe side. |
898 | |
1040 | |
899 | =back |
1041 | =back |
900 | |
1042 | |
901 | |
1043 | |
902 | =head3 FORK WATCHERS - the audacity to resume the event loop after a fork |
1044 | =head3 FORK WATCHERS - the audacity to resume the event loop after a fork |
… | |
… | |
930 | loop, other types of watchers might be handled in a delayed or incorrect |
1072 | loop, other types of watchers might be handled in a delayed or incorrect |
931 | fashion and must not be used). |
1073 | fashion and must not be used). |
932 | |
1074 | |
933 | See the libev documentation at |
1075 | See the libev documentation at |
934 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_> |
1076 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_> |
935 | for more details. |
1077 | (locally installed as F<EV::libev>) for more details. |
936 | |
1078 | |
937 | In short, this watcher is most useful on BSD systems without working |
1079 | In short, this watcher is most useful on BSD systems without working |
938 | kqueue to still be able to handle a large number of sockets: |
1080 | kqueue to still be able to handle a large number of sockets: |
939 | |
1081 | |
940 | my $socket_loop; |
1082 | my $socket_loop; |
941 | |
1083 | |
942 | # check wether we use SELECT or POLL _and_ KQUEUE is supported |
1084 | # check wether we use SELECT or POLL _and_ KQUEUE is supported |
943 | if ( |
1085 | if ( |
944 | (EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT)) |
1086 | (EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT)) |
945 | && (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE) |
1087 | && (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE) |
946 | ) { |
1088 | ) { |
947 | # use kqueue for sockets |
1089 | # use kqueue for sockets |
948 | $socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV; |
1090 | $socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV; |
949 | } |
1091 | } |
950 | |
1092 | |
951 | # use the default loop otherwise |
1093 | # use the default loop otherwise |
952 | $socket_loop ||= EV::default_loop; |
1094 | $socket_loop ||= EV::default_loop; |
953 | |
1095 | |
954 | =over 4 |
1096 | =over 4 |
955 | |
1097 | |
956 | =item $w = EV::embed $otherloop, $callback |
1098 | =item $w = EV::embed $otherloop[, $callback] |
957 | |
1099 | |
958 | =item $w = EV::embed_ns $otherloop, $callback |
1100 | =item $w = EV::embed_ns $otherloop[, $callback] |
959 | |
1101 | |
960 | =item $w = $loop->embed ($otherloop, $callback) |
1102 | =item $w = $loop->embed ($otherloop[, $callback]) |
961 | |
1103 | |
962 | =item $w = $loop->embed_ns ($otherloop, $callback) |
1104 | =item $w = $loop->embed_ns ($otherloop[, $callback]) |
963 | |
1105 | |
964 | Call the callback when the embedded event loop (C<$otherloop>) has any |
1106 | Call the callback when the embedded event loop (C<$otherloop>) has any |
965 | I/O activity. The C<$callback> should alwas be specified as C<undef> in |
1107 | I/O activity. The C<$callback> is optional: if it is missing, then the |
966 | this version of EV, which means the embedded event loop will be managed |
1108 | embedded event loop will be managed automatically (which is recommended), |
967 | automatically. |
1109 | otherwise you have to invoke C<sweep> yourself. |
968 | |
1110 | |
969 | The C<embed_ns> variant doesn't start (activate) the newly created watcher. |
1111 | The C<embed_ns> variant doesn't start (activate) the newly created watcher. |
|
|
1112 | |
|
|
1113 | =back |
|
|
1114 | |
|
|
1115 | =head3 ASYNC WATCHERS - how to wake up another event loop |
|
|
1116 | |
|
|
1117 | Async watchers are provided by EV, but have little use in perl directly, |
|
|
1118 | as perl neither supports threads running in parallel nor direct access to |
|
|
1119 | signal handlers or other contexts where they could be of value. |
|
|
1120 | |
|
|
1121 | It is, however, possible to use them from the XS level. |
|
|
1122 | |
|
|
1123 | Please see the libev documentation for further details. |
|
|
1124 | |
|
|
1125 | =over 4 |
|
|
1126 | |
|
|
1127 | =item $w = EV::async $callback |
|
|
1128 | |
|
|
1129 | =item $w = EV::async_ns $callback |
|
|
1130 | |
|
|
1131 | =item $w->send |
|
|
1132 | |
|
|
1133 | =item $bool = $w->async_pending |
970 | |
1134 | |
971 | =back |
1135 | =back |
972 | |
1136 | |
973 | |
1137 | |
974 | =head1 PERL SIGNALS |
1138 | =head1 PERL SIGNALS |
… | |
… | |
988 | my $async_check = EV::check sub { }; |
1152 | my $async_check = EV::check sub { }; |
989 | |
1153 | |
990 | This ensures that perl gets into control for a short time to handle any |
1154 | This ensures that perl gets into control for a short time to handle any |
991 | pending signals, and also ensures (slightly) slower overall operation. |
1155 | pending signals, and also ensures (slightly) slower overall operation. |
992 | |
1156 | |
993 | =head1 THREADS |
1157 | =head1 ITHREADS |
994 | |
1158 | |
995 | Threads are not supported by this module in any way. Perl pseudo-threads |
1159 | Ithreads are not supported by this module in any way. Perl pseudo-threads |
996 | is evil stuff and must die. As soon as Perl gains real threads I will work |
1160 | is evil stuff and must die. Real threads as provided by Coro are fully |
997 | on thread support for it. |
1161 | supported (and enhanced support is available via L<Coro::EV>). |
998 | |
1162 | |
999 | =head1 FORK |
1163 | =head1 FORK |
1000 | |
1164 | |
1001 | Most of the "improved" event delivering mechanisms of modern operating |
1165 | Most of the "improved" event delivering mechanisms of modern operating |
1002 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
1166 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
… | |
… | |
1024 | |
1188 | |
1025 | 1; |
1189 | 1; |
1026 | |
1190 | |
1027 | =head1 SEE ALSO |
1191 | =head1 SEE ALSO |
1028 | |
1192 | |
|
|
1193 | L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS> |
1029 | L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as |
1194 | (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as event |
1030 | event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient |
1195 | loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient thread |
1031 | coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP). |
1196 | integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for |
|
|
1197 | event-loop agnostic and portable event driven programming. |
1032 | |
1198 | |
1033 | =head1 AUTHOR |
1199 | =head1 AUTHOR |
1034 | |
1200 | |
1035 | Marc Lehmann <schmorp@schmorp.de> |
1201 | Marc Lehmann <schmorp@schmorp.de> |
1036 | http://home.schmorp.de/ |
1202 | http://home.schmorp.de/ |
1037 | |
1203 | |
1038 | =cut |
1204 | =cut |
1039 | |
1205 | |