… | |
… | |
39 | |
39 | |
40 | my $w = EV::child 666, sub { |
40 | my $w = EV::child 666, sub { |
41 | my ($w, $revents) = @_; |
41 | my ($w, $revents) = @_; |
42 | my $status = $w->rstatus; |
42 | my $status = $w->rstatus; |
43 | }; |
43 | }; |
|
|
44 | |
|
|
45 | # STAT CHANGES |
|
|
46 | my $w = EV::stat "/etc/passwd", 10, sub { |
|
|
47 | my ($w, $revents) = @_; |
|
|
48 | warn $w->path, " has changed somehow.\n"; |
|
|
49 | }; |
44 | |
50 | |
45 | # MAINLOOP |
51 | # MAINLOOP |
46 | 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 |
47 | 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 |
48 | 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 |
49 | |
55 | |
50 | =head1 DESCRIPTION |
56 | =head1 DESCRIPTION |
51 | |
57 | |
52 | This module provides an interface to libev |
58 | This module provides an interface to libev |
53 | (L<http://software.schmorp.de/pkg/libev.html>). |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
|
|
60 | below is comprehensive, one might also consult the documentation of libev |
|
|
61 | itself (L<http://cvs.schmorp.de/libev/ev.html>) for more subtle details on |
|
|
62 | watcher semantics or some discussion on the available backends, or how to |
|
|
63 | force a specific backend with C<LIBEV_FLAGS>. |
54 | |
64 | |
55 | =cut |
65 | =cut |
56 | |
66 | |
57 | package EV; |
67 | package EV; |
58 | |
68 | |
59 | use strict; |
69 | use strict; |
60 | |
70 | |
61 | BEGIN { |
71 | BEGIN { |
62 | our $VERSION = '1.0'; |
72 | our $VERSION = '1.5'; |
63 | use XSLoader; |
73 | use XSLoader; |
64 | XSLoader::load "EV", $VERSION; |
74 | XSLoader::load "EV", $VERSION; |
65 | } |
75 | } |
66 | |
76 | |
67 | @EV::Io::ISA = |
77 | @EV::IO::ISA = |
68 | @EV::Timer::ISA = |
78 | @EV::Timer::ISA = |
69 | @EV::Periodic::ISA = |
79 | @EV::Periodic::ISA = |
70 | @EV::Signal::ISA = |
80 | @EV::Signal::ISA = |
|
|
81 | @EV::Child::ISA = |
|
|
82 | @EV::Stat::ISA = |
71 | @EV::Idle::ISA = |
83 | @EV::Idle::ISA = |
72 | @EV::Prepare::ISA = |
84 | @EV::Prepare::ISA = |
73 | @EV::Check::ISA = |
85 | @EV::Check::ISA = |
74 | @EV::Child::ISA = "EV::Watcher"; |
86 | @EV::Embed::ISA = |
|
|
87 | @EV::Fork::ISA = |
|
|
88 | "EV::Watcher"; |
75 | |
89 | |
76 | =head1 BASIC INTERFACE |
90 | =head1 BASIC INTERFACE |
77 | |
91 | |
78 | =over 4 |
92 | =over 4 |
79 | |
93 | |
… | |
… | |
117 | innermost call to EV::loop return. |
131 | innermost call to EV::loop return. |
118 | |
132 | |
119 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
133 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
120 | fast as possible. |
134 | fast as possible. |
121 | |
135 | |
122 | =back |
136 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
123 | |
137 | |
|
|
138 | This function rolls together an I/O and a timer watcher for a single |
|
|
139 | one-shot event without the need for managing a watcher object. |
|
|
140 | |
|
|
141 | If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events> |
|
|
142 | must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ |
|
|
143 | | EV::WRITE>, indicating the type of I/O event you want to wait for. If |
|
|
144 | you do not want to wait for some I/O event, specify C<undef> for |
|
|
145 | C<$fh_or_undef> and C<0> for C<$events>). |
|
|
146 | |
|
|
147 | If timeout is C<undef> or negative, then there will be no |
|
|
148 | timeout. Otherwise a EV::timer with this value will be started. |
|
|
149 | |
|
|
150 | When an error occurs or either the timeout or I/O watcher triggers, then |
|
|
151 | the callback will be called with the received event set (in general |
|
|
152 | you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>, |
|
|
153 | C<EV::WRITE> and C<EV::TIMEOUT>). |
|
|
154 | |
|
|
155 | EV::once doesn't return anything: the watchers stay active till either |
|
|
156 | of them triggers, then they will be stopped and freed, and the callback |
|
|
157 | invoked. |
|
|
158 | |
|
|
159 | =back |
|
|
160 | |
124 | =head2 WATCHER |
161 | =head2 WATCHER OBJECTS |
125 | |
162 | |
126 | A watcher is an object that gets created to record your interest in some |
163 | A watcher is an object that gets created to record your interest in some |
127 | event. For instance, if you want to wait for STDIN to become readable, you |
164 | event. For instance, if you want to wait for STDIN to become readable, you |
128 | would create an EV::io watcher for that: |
165 | would create an EV::io watcher for that: |
129 | |
166 | |
… | |
… | |
154 | |
191 | |
155 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
192 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
156 | ->fh and so on) automatically stop and start it again if it is active, |
193 | ->fh and so on) automatically stop and start it again if it is active, |
157 | which means pending events get lost. |
194 | which means pending events get lost. |
158 | |
195 | |
159 | =head2 WATCHER TYPES |
196 | =head2 COMMON WATCHER METHODS |
160 | |
197 | |
161 | Now lets move to the existing watcher types and asociated methods. |
198 | This section lists methods common to all watchers. |
162 | |
|
|
163 | The following methods are available for all watchers. Then followes a |
|
|
164 | description of each watcher constructor (EV::io, EV::timer, EV::periodic, |
|
|
165 | EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by |
|
|
166 | any type-specific methods (if any). |
|
|
167 | |
199 | |
168 | =over 4 |
200 | =over 4 |
169 | |
201 | |
170 | =item $w->start |
202 | =item $w->start |
171 | |
203 | |
… | |
… | |
210 | watchers with higher priority will be invoked first. The valid range of |
242 | watchers with higher priority will be invoked first. The valid range of |
211 | priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default |
243 | priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default |
212 | -2). If the priority is outside this range it will automatically be |
244 | -2). If the priority is outside this range it will automatically be |
213 | normalised to the nearest valid priority. |
245 | normalised to the nearest valid priority. |
214 | |
246 | |
215 | The default priority of any newly-created weatcher is 0. |
247 | The default priority of any newly-created watcher is 0. |
|
|
248 | |
|
|
249 | Note that the priority semantics have not yet been fleshed out and are |
|
|
250 | subject to almost certain change. |
216 | |
251 | |
217 | =item $w->trigger ($revents) |
252 | =item $w->trigger ($revents) |
218 | |
253 | |
219 | Call the callback *now* with the given event mask. |
254 | Call the callback *now* with the given event mask. |
220 | |
255 | |
|
|
256 | =item $previous_state = $w->keepalive ($bool) |
|
|
257 | |
|
|
258 | Normally, C<EV::loop> will return when there are no active watchers |
|
|
259 | (which is a "deadlock" because no progress can be made anymore). This is |
|
|
260 | convinient because it allows you to start your watchers (and your jobs), |
|
|
261 | call C<EV::loop> once and when it returns you know that all your jobs are |
|
|
262 | finished (or they forgot to register some watchers for their task :). |
|
|
263 | |
|
|
264 | Sometimes, however, this gets in your way, for example when you the module |
|
|
265 | that calls C<EV::loop> (usually the main program) is not the same module |
|
|
266 | as a long-living watcher (for example a DNS client module written by |
|
|
267 | somebody else even). Then you might want any outstanding requests to be |
|
|
268 | handled, but you would not want to keep C<EV::loop> from returning just |
|
|
269 | because you happen to have this long-running UDP port watcher. |
|
|
270 | |
|
|
271 | In this case you can clear the keepalive status, which means that even |
|
|
272 | though your watcher is active, it won't keep C<EV::loop> from returning. |
|
|
273 | |
|
|
274 | The initial value for keepalive is true (enabled), and you cna change it |
|
|
275 | any time. |
|
|
276 | |
|
|
277 | Example: Register an IO watcher for some UDP socket but do not keep the |
|
|
278 | event loop from running just because of that watcher. |
|
|
279 | |
|
|
280 | my $udp_socket = ... |
|
|
281 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
|
|
282 | $udp_watcher->keepalive (0); |
|
|
283 | |
|
|
284 | =back |
|
|
285 | |
|
|
286 | |
|
|
287 | =head2 WATCHER TYPES |
|
|
288 | |
|
|
289 | Each of the following subsections describes a single watcher type. |
|
|
290 | |
|
|
291 | =head3 IO WATCHERS - is this file descriptor readable or writable? |
|
|
292 | |
|
|
293 | =over 4 |
221 | |
294 | |
222 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
295 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
223 | |
296 | |
224 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
297 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
225 | |
298 | |
226 | As long as the returned watcher object is alive, call the C<$callback> |
299 | As long as the returned watcher object is alive, call the C<$callback> |
227 | when the events specified in C<$eventmask>. |
300 | when at least one of events specified in C<$eventmask> occurs. |
228 | |
301 | |
229 | The $eventmask can be one or more of these constants ORed together: |
302 | The $eventmask can be one or more of these constants ORed together: |
230 | |
303 | |
231 | EV::READ wait until read() wouldn't block anymore |
304 | EV::READ wait until read() wouldn't block anymore |
232 | EV::WRITE wait until write() wouldn't block anymore |
305 | EV::WRITE wait until write() wouldn't block anymore |
… | |
… | |
248 | |
321 | |
249 | =item $old_eventmask = $w->events ($new_eventmask) |
322 | =item $old_eventmask = $w->events ($new_eventmask) |
250 | |
323 | |
251 | Returns the previously set event mask and optionally set a new one. |
324 | Returns the previously set event mask and optionally set a new one. |
252 | |
325 | |
|
|
326 | =back |
|
|
327 | |
|
|
328 | |
|
|
329 | =head3 TIMER WATCHERS - relative and optionally repeating timeouts |
|
|
330 | |
|
|
331 | =over 4 |
253 | |
332 | |
254 | =item $w = EV::timer $after, $repeat, $callback |
333 | =item $w = EV::timer $after, $repeat, $callback |
255 | |
334 | |
256 | =item $w = EV::timer_ns $after, $repeat, $callback |
335 | =item $w = EV::timer_ns $after, $repeat, $callback |
257 | |
336 | |
258 | Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, |
337 | Calls the callback after C<$after> seconds (which may be fractional). If |
259 | the timer will be restarted (with the $repeat value as $after) after the |
338 | C<$repeat> is non-zero, the timer will be restarted (with the $repeat |
260 | callback returns. |
339 | value as $after) after the callback returns. |
261 | |
340 | |
262 | This means that the callback would be called roughly after C<$after> |
341 | This means that the callback would be called roughly after C<$after> |
263 | seconds, and then every C<$repeat> seconds. The timer does his best not |
342 | seconds, and then every C<$repeat> seconds. The timer does his best not |
264 | to drift, but it will not invoke the timer more often then once per event |
343 | to drift, but it will not invoke the timer more often then once per event |
265 | loop iteration, and might drift in other cases. If that isn't acceptable, |
344 | loop iteration, and might drift in other cases. If that isn't acceptable, |
… | |
… | |
271 | |
350 | |
272 | The C<timer_ns> variant doesn't start (activate) the newly created watcher. |
351 | The C<timer_ns> variant doesn't start (activate) the newly created watcher. |
273 | |
352 | |
274 | =item $w->set ($after, $repeat) |
353 | =item $w->set ($after, $repeat) |
275 | |
354 | |
276 | Reconfigures the watcher, see the constructor above for details. Can be at |
355 | Reconfigures the watcher, see the constructor above for details. Can be called at |
277 | any time. |
356 | any time. |
278 | |
357 | |
279 | =item $w->again |
358 | =item $w->again |
280 | |
359 | |
281 | Similar to the C<start> method, but has special semantics for repeating timers: |
360 | Similar to the C<start> method, but has special semantics for repeating timers: |
… | |
… | |
292 | This behaviour is useful when you have a timeout for some IO |
371 | This behaviour is useful when you have a timeout for some IO |
293 | operation. You create a timer object with the same value for C<$after> and |
372 | operation. You create a timer object with the same value for C<$after> and |
294 | C<$repeat>, and then, in the read/write watcher, run the C<again> method |
373 | C<$repeat>, and then, in the read/write watcher, run the C<again> method |
295 | on the timeout. |
374 | on the timeout. |
296 | |
375 | |
|
|
376 | =back |
|
|
377 | |
|
|
378 | |
|
|
379 | =head3 PERIODIC WATCHERS - to cron or not to cron? |
|
|
380 | |
|
|
381 | =over 4 |
297 | |
382 | |
298 | =item $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
383 | =item $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
299 | |
384 | |
300 | =item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
385 | =item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
301 | |
386 | |
… | |
… | |
373 | |
458 | |
374 | The C<periodic_ns> variant doesn't start (activate) the newly created watcher. |
459 | The C<periodic_ns> variant doesn't start (activate) the newly created watcher. |
375 | |
460 | |
376 | =item $w->set ($at, $interval, $reschedule_cb) |
461 | =item $w->set ($at, $interval, $reschedule_cb) |
377 | |
462 | |
378 | Reconfigures the watcher, see the constructor above for details. Can be at |
463 | Reconfigures the watcher, see the constructor above for details. Can be called at |
379 | any time. |
464 | any time. |
380 | |
465 | |
381 | =item $w->again |
466 | =item $w->again |
382 | |
467 | |
383 | Simply stops and starts the watcher again. |
468 | Simply stops and starts the watcher again. |
384 | |
469 | |
|
|
470 | =back |
|
|
471 | |
|
|
472 | |
|
|
473 | =head3 SIGNAL WATCHERS - signal me when a signal gets signalled! |
|
|
474 | |
|
|
475 | =over 4 |
385 | |
476 | |
386 | =item $w = EV::signal $signal, $callback |
477 | =item $w = EV::signal $signal, $callback |
387 | |
478 | |
388 | =item $w = EV::signal_ns $signal, $callback |
479 | =item $w = EV::signal_ns $signal, $callback |
389 | |
480 | |
390 | Call the callback when $signal is received (the signal can be specified |
481 | Call the callback when $signal is received (the signal can be specified by |
391 | by number or by name, just as with kill or %SIG). |
482 | number or by name, just as with C<kill> or C<%SIG>). |
392 | |
483 | |
393 | EV will grab the signal for the process (the kernel only allows one |
484 | EV will grab the signal for the process (the kernel only allows one |
394 | component to receive a signal at a time) when you start a signal watcher, |
485 | component to receive a signal at a time) when you start a signal watcher, |
395 | and removes it again when you stop it. Perl does the same when you |
486 | and removes it again when you stop it. Perl does the same when you |
396 | add/remove callbacks to %SIG, so watch out. |
487 | add/remove callbacks to C<%SIG>, so watch out. |
397 | |
488 | |
398 | You can have as many signal watchers per signal as you want. |
489 | You can have as many signal watchers per signal as you want. |
399 | |
490 | |
400 | The C<signal_ns> variant doesn't start (activate) the newly created watcher. |
491 | The C<signal_ns> variant doesn't start (activate) the newly created watcher. |
401 | |
492 | |
402 | =item $w->set ($signal) |
493 | =item $w->set ($signal) |
403 | |
494 | |
404 | Reconfigures the watcher, see the constructor above for details. Can be at |
495 | Reconfigures the watcher, see the constructor above for details. Can be |
405 | any time. |
496 | called at any time. |
406 | |
497 | |
407 | =item $current_signum = $w->signal |
498 | =item $current_signum = $w->signal |
408 | |
499 | |
409 | =item $old_signum = $w->signal ($new_signal) |
500 | =item $old_signum = $w->signal ($new_signal) |
410 | |
501 | |
411 | Returns the previously set signal (always as a number not name) and |
502 | Returns the previously set signal (always as a number not name) and |
412 | optionally set a new one. |
503 | optionally set a new one. |
413 | |
504 | |
|
|
505 | =back |
|
|
506 | |
|
|
507 | |
|
|
508 | =head3 CHILD WATCHERS - watch out for process status changes |
|
|
509 | |
|
|
510 | =over 4 |
414 | |
511 | |
415 | =item $w = EV::child $pid, $callback |
512 | =item $w = EV::child $pid, $callback |
416 | |
513 | |
417 | =item $w = EV::child_ns $pid, $callback |
514 | =item $w = EV::child_ns $pid, $callback |
418 | |
515 | |
419 | Call the callback when a status change for pid C<$pid> (or any pid |
516 | Call the callback when a status change for pid C<$pid> (or any pid if |
420 | if C<$pid> is 0) has been received. More precisely: when the process |
517 | C<$pid> is 0) has been received. More precisely: when the process receives |
421 | receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all |
518 | a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all |
422 | changed/zombie children and call the callback. |
519 | changed/zombie children and call the callback. |
423 | |
520 | |
424 | You can access both status and pid by using the C<rstatus> and C<rpid> |
521 | It is valid (and fully supported) to install a child watcher after a child |
425 | methods on the watcher object. |
522 | has exited but before the event loop has started its next iteration (for |
|
|
523 | example, first you C<fork>, then the new child process might exit, and |
|
|
524 | only then do you install a child watcher in the parent for the new pid). |
426 | |
525 | |
|
|
526 | You can access both exit (or tracing) status and pid by using the |
|
|
527 | C<rstatus> and C<rpid> methods on the watcher object. |
|
|
528 | |
427 | You can have as many pid watchers per pid as you want. |
529 | You can have as many pid watchers per pid as you want, they will all be |
|
|
530 | called. |
428 | |
531 | |
429 | The C<child_ns> variant doesn't start (activate) the newly created watcher. |
532 | The C<child_ns> variant doesn't start (activate) the newly created watcher. |
430 | |
533 | |
431 | =item $w->set ($pid) |
534 | =item $w->set ($pid) |
432 | |
535 | |
433 | Reconfigures the watcher, see the constructor above for details. Can be at |
536 | Reconfigures the watcher, see the constructor above for details. Can be called at |
434 | any time. |
537 | any time. |
435 | |
538 | |
436 | =item $current_pid = $w->pid |
539 | =item $current_pid = $w->pid |
437 | |
540 | |
438 | =item $old_pid = $w->pid ($new_pid) |
541 | =item $old_pid = $w->pid ($new_pid) |
… | |
… | |
447 | =item $pid = $w->rpid |
550 | =item $pid = $w->rpid |
448 | |
551 | |
449 | Return the pid of the awaited child (useful when you have installed a |
552 | Return the pid of the awaited child (useful when you have installed a |
450 | watcher for all pids). |
553 | watcher for all pids). |
451 | |
554 | |
|
|
555 | =back |
|
|
556 | |
|
|
557 | |
|
|
558 | =head3 STAT WATCHERS - did the file attributes just change? |
|
|
559 | |
|
|
560 | =over 4 |
|
|
561 | |
|
|
562 | =item $w = EV::stat $path, $interval, $callback |
|
|
563 | |
|
|
564 | =item $w = EV::stat_ns $path, $interval, $callback |
|
|
565 | |
|
|
566 | Call the callback when a file status change has been detected on |
|
|
567 | C<$path>. The C<$path> does not need to exist, changing from "path exists" |
|
|
568 | to "path does not exist" is a status change like any other. |
|
|
569 | |
|
|
570 | The C<$interval> is a recommended polling interval for systems where |
|
|
571 | OS-supported change notifications don't exist or are not supported. If |
|
|
572 | you use C<0> then an unspecified default is used (which is highly |
|
|
573 | recommended!), which is to be expected to be around five seconds usually. |
|
|
574 | |
|
|
575 | This watcher type is not meant for massive numbers of stat watchers, |
|
|
576 | as even with OS-supported change notifications, this can be |
|
|
577 | resource-intensive. |
|
|
578 | |
|
|
579 | The C<stat_ns> variant doesn't start (activate) the newly created watcher. |
|
|
580 | |
|
|
581 | =item ... = $w->stat |
|
|
582 | |
|
|
583 | This call is very similar to the perl C<stat> built-in: It stats (using |
|
|
584 | C<lstat>) the path specified in the watcher and sets perls stat cache (as |
|
|
585 | well as EV's idea of the current stat values) to the values found. |
|
|
586 | |
|
|
587 | In scalar context, a boolean is return indicating success or failure of |
|
|
588 | the stat. In list context, the same 13-value list as with stat is returned |
|
|
589 | (except that the blksize and blocks fields are not reliable). |
|
|
590 | |
|
|
591 | In the case of an error, errno is set to C<ENOENT> (regardless of the |
|
|
592 | actual error value) and the C<nlink> value is forced to zero (if the stat |
|
|
593 | was successful then nlink is guaranteed to be non-zero). |
|
|
594 | |
|
|
595 | See also the next two entries for more info. |
|
|
596 | |
|
|
597 | =item ... = $w->attr |
|
|
598 | |
|
|
599 | Just like C<< $w->stat >>, but without the initial stat'ing: this returns |
|
|
600 | the values most recently detected by EV. See the next entry for more info. |
|
|
601 | |
|
|
602 | =item ... = $w->prev |
|
|
603 | |
|
|
604 | Just like C<< $w->stat >>, but without the initial stat'ing: this returns |
|
|
605 | the previous set of values, before the change. |
|
|
606 | |
|
|
607 | That is, when the watcher callback is invoked, C<< $w->prev >> will be set |
|
|
608 | to the values found I<before> a change was detected, while C<< $w->attr >> |
|
|
609 | returns the values found leading to the change detection. The difference (if any) |
|
|
610 | between C<prev> and C<attr> is what triggered the callback. |
|
|
611 | |
|
|
612 | If you did something to the filesystem object and do not want to trigger |
|
|
613 | yet another change, you can call C<stat> to update EV's idea of what the |
|
|
614 | current attributes are. |
|
|
615 | |
|
|
616 | =item $w->set ($path, $interval) |
|
|
617 | |
|
|
618 | Reconfigures the watcher, see the constructor above for details. Can be |
|
|
619 | called at any time. |
|
|
620 | |
|
|
621 | =item $current_path = $w->path |
|
|
622 | |
|
|
623 | =item $old_path = $w->path ($new_path) |
|
|
624 | |
|
|
625 | Returns the previously set path and optionally set a new one. |
|
|
626 | |
|
|
627 | =item $current_interval = $w->interval |
|
|
628 | |
|
|
629 | =item $old_interval = $w->interval ($new_interval) |
|
|
630 | |
|
|
631 | Returns the previously set interval and optionally set a new one. Can be |
|
|
632 | used to query the actual interval used. |
|
|
633 | |
|
|
634 | =back |
|
|
635 | |
|
|
636 | |
|
|
637 | =head3 IDLE WATCHERS - when you've got nothing better to do... |
|
|
638 | |
|
|
639 | =over 4 |
452 | |
640 | |
453 | =item $w = EV::idle $callback |
641 | =item $w = EV::idle $callback |
454 | |
642 | |
455 | =item $w = EV::idle_ns $callback |
643 | =item $w = EV::idle_ns $callback |
456 | |
644 | |
… | |
… | |
460 | The process will not block as long as any idle watchers are active, and |
648 | The process will not block as long as any idle watchers are active, and |
461 | they will be called repeatedly until stopped. |
649 | they will be called repeatedly until stopped. |
462 | |
650 | |
463 | The C<idle_ns> variant doesn't start (activate) the newly created watcher. |
651 | The C<idle_ns> variant doesn't start (activate) the newly created watcher. |
464 | |
652 | |
|
|
653 | =back |
|
|
654 | |
|
|
655 | |
|
|
656 | =head3 PREPARE WATCHERS - customise your event loop! |
|
|
657 | |
|
|
658 | =over 4 |
465 | |
659 | |
466 | =item $w = EV::prepare $callback |
660 | =item $w = EV::prepare $callback |
467 | |
661 | |
468 | =item $w = EV::prepare_ns $callback |
662 | =item $w = EV::prepare_ns $callback |
469 | |
663 | |
… | |
… | |
472 | |
666 | |
473 | See the EV::check watcher, below, for explanations and an example. |
667 | See the EV::check watcher, below, for explanations and an example. |
474 | |
668 | |
475 | The C<prepare_ns> variant doesn't start (activate) the newly created watcher. |
669 | The C<prepare_ns> variant doesn't start (activate) the newly created watcher. |
476 | |
670 | |
|
|
671 | =back |
|
|
672 | |
|
|
673 | |
|
|
674 | =head3 CHECK WATCHERS - customise your event loop even more! |
|
|
675 | |
|
|
676 | =over 4 |
477 | |
677 | |
478 | =item $w = EV::check $callback |
678 | =item $w = EV::check $callback |
479 | |
679 | |
480 | =item $w = EV::check_ns $callback |
680 | =item $w = EV::check_ns $callback |
481 | |
681 | |
… | |
… | |
493 | # do nothing unless active |
693 | # do nothing unless active |
494 | $dispatcher->{_event_queue_h} |
694 | $dispatcher->{_event_queue_h} |
495 | or return; |
695 | or return; |
496 | |
696 | |
497 | # make the dispatcher handle any outstanding stuff |
697 | # make the dispatcher handle any outstanding stuff |
|
|
698 | ... not shown |
498 | |
699 | |
499 | # create an IO watcher for each and every socket |
700 | # create an IO watcher for each and every socket |
500 | @snmp_watcher = ( |
701 | @snmp_watcher = ( |
501 | (map { EV::io $_, EV::READ, sub { } } |
702 | (map { EV::io $_, EV::READ, sub { } } |
502 | keys %{ $dispatcher->{_descriptors} }), |
703 | keys %{ $dispatcher->{_descriptors} }), |
|
|
704 | |
|
|
705 | EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] |
|
|
706 | ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0), |
|
|
707 | 0, sub { }, |
503 | ); |
708 | ); |
504 | |
|
|
505 | # if there are any timeouts, also create a timer |
|
|
506 | push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { } |
|
|
507 | if $event->[Net::SNMP::Dispatcher::_ACTIVE]; |
|
|
508 | }; |
709 | }; |
509 | |
710 | |
510 | The callbacks are irrelevant, the only purpose of those watchers is |
711 | The callbacks are irrelevant (and are not even being called), the |
511 | to wake up the process as soon as one of those events occurs (socket |
712 | only purpose of those watchers is to wake up the process as soon as |
512 | readable, or timer timed out). The corresponding EV::check watcher will then |
713 | one of those events occurs (socket readable, or timer timed out). The |
513 | clean up: |
714 | corresponding EV::check watcher will then clean up: |
514 | |
715 | |
515 | our $snmp_check = EV::check sub { |
716 | our $snmp_check = EV::check sub { |
516 | # destroy all watchers |
717 | # destroy all watchers |
517 | @snmp_watcher = (); |
718 | @snmp_watcher = (); |
518 | |
719 | |
519 | # make the dispatcher handle any new stuff |
720 | # make the dispatcher handle any new stuff |
|
|
721 | ... not shown |
520 | }; |
722 | }; |
521 | |
723 | |
522 | The callbacks of the created watchers will not be called as the watchers |
724 | The callbacks of the created watchers will not be called as the watchers |
523 | are destroyed before this cna happen (remember EV::check gets called |
725 | are destroyed before this cna happen (remember EV::check gets called |
524 | first). |
726 | first). |
525 | |
727 | |
526 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
728 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
527 | |
729 | |
528 | =back |
730 | =back |
529 | |
731 | |
|
|
732 | |
|
|
733 | =head3 FORK WATCHERS - the audacity to resume the event loop after a fork |
|
|
734 | |
|
|
735 | Fork watchers are called when a C<fork ()> was detected. The invocation |
|
|
736 | is done before the event loop blocks next and before C<check> watchers |
|
|
737 | are being called, and only in the child after the fork. |
|
|
738 | |
|
|
739 | =over 4 |
|
|
740 | |
|
|
741 | =item $w = EV::fork $callback |
|
|
742 | |
|
|
743 | =item $w = EV::fork_ns $callback |
|
|
744 | |
|
|
745 | Call the callback before the event loop is resumed in the child process |
|
|
746 | after a fork. |
|
|
747 | |
|
|
748 | The C<fork_ns> variant doesn't start (activate) the newly created watcher. |
|
|
749 | |
|
|
750 | =back |
|
|
751 | |
|
|
752 | |
530 | =head1 THREADS |
753 | =head1 THREADS |
531 | |
754 | |
532 | Threads are not supported by this in any way. Perl pseudo-threads is evil |
755 | Threads are not supported by this module in any way. Perl pseudo-threads |
533 | stuff and must die. |
756 | is evil stuff and must die. As soon as Perl gains real threads I will work |
|
|
757 | on thread support for it. |
|
|
758 | |
|
|
759 | =head1 FORK |
|
|
760 | |
|
|
761 | Most of the "improved" event delivering mechanisms of modern operating |
|
|
762 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
|
|
763 | not supported and usually destructive). Libev makes it possible to work |
|
|
764 | around this by having a function that recreates the kernel state after |
|
|
765 | fork in the child. |
|
|
766 | |
|
|
767 | On non-win32 platforms, this module requires the pthread_atfork |
|
|
768 | functionality to do this automatically for you. This function is quite |
|
|
769 | buggy on most BSDs, though, so YMMV. The overhead for this is quite |
|
|
770 | negligible, because everything the function currently does is set a flag |
|
|
771 | that is checked only when the event loop gets used the next time, so when |
|
|
772 | you do fork but not use EV, the overhead is minimal. |
|
|
773 | |
|
|
774 | On win32, there is no notion of fork so all this doesn't apply, of course. |
534 | |
775 | |
535 | =cut |
776 | =cut |
536 | |
777 | |
537 | our $DIED = sub { |
778 | our $DIED = sub { |
538 | warn "EV: error in callback (ignoring): $@"; |
779 | warn "EV: error in callback (ignoring): $@"; |
… | |
… | |
543 | |
784 | |
544 | 1; |
785 | 1; |
545 | |
786 | |
546 | =head1 SEE ALSO |
787 | =head1 SEE ALSO |
547 | |
788 | |
548 | L<EV::DNS>. |
789 | L<EV::ADNS> (asynchronous dns), L<Glib::EV> (makes Glib/Gtk2 use EV as |
|
|
790 | event loop), L<Coro::EV> (efficient coroutines with EV). |
549 | |
791 | |
550 | =head1 AUTHOR |
792 | =head1 AUTHOR |
551 | |
793 | |
552 | Marc Lehmann <schmorp@schmorp.de> |
794 | Marc Lehmann <schmorp@schmorp.de> |
553 | http://home.schmorp.de/ |
795 | http://home.schmorp.de/ |