… | |
… | |
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.2'; |
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 | |
… | |
… | |
142 | of them triggers, then they will be stopped and freed, and the callback |
156 | of them triggers, then they will be stopped and freed, and the callback |
143 | invoked. |
157 | invoked. |
144 | |
158 | |
145 | =back |
159 | =back |
146 | |
160 | |
147 | =head2 WATCHER |
161 | =head2 WATCHER OBJECTS |
148 | |
162 | |
149 | 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 |
150 | 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 |
151 | would create an EV::io watcher for that: |
165 | would create an EV::io watcher for that: |
152 | |
166 | |
… | |
… | |
177 | |
191 | |
178 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
192 | Also, all methods changing some aspect of a watcher (->set, ->priority, |
179 | ->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, |
180 | which means pending events get lost. |
194 | which means pending events get lost. |
181 | |
195 | |
182 | =head2 WATCHER TYPES |
196 | =head2 COMMON WATCHER METHODS |
183 | |
197 | |
184 | Now lets move to the existing watcher types and asociated methods. |
198 | This section lists methods common to all watchers. |
185 | |
|
|
186 | The following methods are available for all watchers. Then followes a |
|
|
187 | description of each watcher constructor (EV::io, EV::timer, EV::periodic, |
|
|
188 | EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by |
|
|
189 | any type-specific methods (if any). |
|
|
190 | |
199 | |
191 | =over 4 |
200 | =over 4 |
192 | |
201 | |
193 | =item $w->start |
202 | =item $w->start |
194 | |
203 | |
… | |
… | |
233 | 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 |
234 | priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default |
243 | priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default |
235 | -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 |
236 | normalised to the nearest valid priority. |
245 | normalised to the nearest valid priority. |
237 | |
246 | |
238 | 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. |
239 | |
251 | |
240 | =item $w->trigger ($revents) |
252 | =item $w->trigger ($revents) |
241 | |
253 | |
242 | Call the callback *now* with the given event mask. |
254 | Call the callback *now* with the given event mask. |
243 | |
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 |
244 | |
294 | |
245 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
295 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
246 | |
296 | |
247 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
297 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
248 | |
298 | |
249 | 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> |
250 | when the events specified in C<$eventmask>. |
300 | when at least one of events specified in C<$eventmask> occurs. |
251 | |
301 | |
252 | 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: |
253 | |
303 | |
254 | EV::READ wait until read() wouldn't block anymore |
304 | EV::READ wait until read() wouldn't block anymore |
255 | EV::WRITE wait until write() wouldn't block anymore |
305 | EV::WRITE wait until write() wouldn't block anymore |
… | |
… | |
271 | |
321 | |
272 | =item $old_eventmask = $w->events ($new_eventmask) |
322 | =item $old_eventmask = $w->events ($new_eventmask) |
273 | |
323 | |
274 | 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. |
275 | |
325 | |
|
|
326 | =back |
|
|
327 | |
|
|
328 | |
|
|
329 | =head3 TIMER WATCHERS - relative and optionally repeating timeouts |
|
|
330 | |
|
|
331 | =over 4 |
276 | |
332 | |
277 | =item $w = EV::timer $after, $repeat, $callback |
333 | =item $w = EV::timer $after, $repeat, $callback |
278 | |
334 | |
279 | =item $w = EV::timer_ns $after, $repeat, $callback |
335 | =item $w = EV::timer_ns $after, $repeat, $callback |
280 | |
336 | |
281 | 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 |
282 | 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 |
283 | callback returns. |
339 | value as $after) after the callback returns. |
284 | |
340 | |
285 | 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> |
286 | 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 |
287 | 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 |
288 | 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, |
… | |
… | |
294 | |
350 | |
295 | 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. |
296 | |
352 | |
297 | =item $w->set ($after, $repeat) |
353 | =item $w->set ($after, $repeat) |
298 | |
354 | |
299 | 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 |
300 | any time. |
356 | any time. |
301 | |
357 | |
302 | =item $w->again |
358 | =item $w->again |
303 | |
359 | |
304 | 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: |
… | |
… | |
315 | 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 |
316 | 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 |
317 | 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 |
318 | on the timeout. |
374 | on the timeout. |
319 | |
375 | |
|
|
376 | =back |
|
|
377 | |
|
|
378 | |
|
|
379 | =head3 PERIODIC WATCHERS - to cron or not to cron? |
|
|
380 | |
|
|
381 | =over 4 |
320 | |
382 | |
321 | =item $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
383 | =item $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
322 | |
384 | |
323 | =item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
385 | =item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
324 | |
386 | |
… | |
… | |
396 | |
458 | |
397 | 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. |
398 | |
460 | |
399 | =item $w->set ($at, $interval, $reschedule_cb) |
461 | =item $w->set ($at, $interval, $reschedule_cb) |
400 | |
462 | |
401 | 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 |
402 | any time. |
464 | any time. |
403 | |
465 | |
404 | =item $w->again |
466 | =item $w->again |
405 | |
467 | |
406 | Simply stops and starts the watcher again. |
468 | Simply stops and starts the watcher again. |
407 | |
469 | |
|
|
470 | =back |
|
|
471 | |
|
|
472 | |
|
|
473 | =head3 SIGNAL WATCHERS - signal me when a signal gets signalled! |
|
|
474 | |
|
|
475 | =over 4 |
408 | |
476 | |
409 | =item $w = EV::signal $signal, $callback |
477 | =item $w = EV::signal $signal, $callback |
410 | |
478 | |
411 | =item $w = EV::signal_ns $signal, $callback |
479 | =item $w = EV::signal_ns $signal, $callback |
412 | |
480 | |
413 | 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 |
414 | by number or by name, just as with kill or %SIG). |
482 | number or by name, just as with C<kill> or C<%SIG>). |
415 | |
483 | |
416 | 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 |
417 | 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, |
418 | 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 |
419 | add/remove callbacks to %SIG, so watch out. |
487 | add/remove callbacks to C<%SIG>, so watch out. |
420 | |
488 | |
421 | 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. |
422 | |
490 | |
423 | 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. |
424 | |
492 | |
425 | =item $w->set ($signal) |
493 | =item $w->set ($signal) |
426 | |
494 | |
427 | Reconfigures the watcher, see the constructor above for details. Can be at |
495 | Reconfigures the watcher, see the constructor above for details. Can be |
428 | any time. |
496 | called at any time. |
429 | |
497 | |
430 | =item $current_signum = $w->signal |
498 | =item $current_signum = $w->signal |
431 | |
499 | |
432 | =item $old_signum = $w->signal ($new_signal) |
500 | =item $old_signum = $w->signal ($new_signal) |
433 | |
501 | |
434 | 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 |
435 | optionally set a new one. |
503 | optionally set a new one. |
436 | |
504 | |
|
|
505 | =back |
|
|
506 | |
|
|
507 | |
|
|
508 | =head3 CHILD WATCHERS - watch out for process status changes |
|
|
509 | |
|
|
510 | =over 4 |
437 | |
511 | |
438 | =item $w = EV::child $pid, $callback |
512 | =item $w = EV::child $pid, $callback |
439 | |
513 | |
440 | =item $w = EV::child_ns $pid, $callback |
514 | =item $w = EV::child_ns $pid, $callback |
441 | |
515 | |
442 | 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 |
443 | 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 |
444 | 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 |
445 | changed/zombie children and call the callback. |
519 | changed/zombie children and call the callback. |
446 | |
520 | |
447 | 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 |
448 | 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). |
449 | |
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 | |
450 | 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. |
451 | |
531 | |
452 | 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. |
453 | |
533 | |
454 | =item $w->set ($pid) |
534 | =item $w->set ($pid) |
455 | |
535 | |
456 | 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 |
457 | any time. |
537 | any time. |
458 | |
538 | |
459 | =item $current_pid = $w->pid |
539 | =item $current_pid = $w->pid |
460 | |
540 | |
461 | =item $old_pid = $w->pid ($new_pid) |
541 | =item $old_pid = $w->pid ($new_pid) |
… | |
… | |
470 | =item $pid = $w->rpid |
550 | =item $pid = $w->rpid |
471 | |
551 | |
472 | 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 |
473 | watcher for all pids). |
553 | watcher for all pids). |
474 | |
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 |
475 | |
640 | |
476 | =item $w = EV::idle $callback |
641 | =item $w = EV::idle $callback |
477 | |
642 | |
478 | =item $w = EV::idle_ns $callback |
643 | =item $w = EV::idle_ns $callback |
479 | |
644 | |
… | |
… | |
483 | 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 |
484 | they will be called repeatedly until stopped. |
649 | they will be called repeatedly until stopped. |
485 | |
650 | |
486 | 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. |
487 | |
652 | |
|
|
653 | =back |
|
|
654 | |
|
|
655 | |
|
|
656 | =head3 PREPARE WATCHERS - customise your event loop! |
|
|
657 | |
|
|
658 | =over 4 |
488 | |
659 | |
489 | =item $w = EV::prepare $callback |
660 | =item $w = EV::prepare $callback |
490 | |
661 | |
491 | =item $w = EV::prepare_ns $callback |
662 | =item $w = EV::prepare_ns $callback |
492 | |
663 | |
… | |
… | |
495 | |
666 | |
496 | See the EV::check watcher, below, for explanations and an example. |
667 | See the EV::check watcher, below, for explanations and an example. |
497 | |
668 | |
498 | 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. |
499 | |
670 | |
|
|
671 | =back |
|
|
672 | |
|
|
673 | |
|
|
674 | =head3 CHECK WATCHERS - customise your event loop even more! |
|
|
675 | |
|
|
676 | =over 4 |
500 | |
677 | |
501 | =item $w = EV::check $callback |
678 | =item $w = EV::check $callback |
502 | |
679 | |
503 | =item $w = EV::check_ns $callback |
680 | =item $w = EV::check_ns $callback |
504 | |
681 | |
… | |
… | |
549 | first). |
726 | first). |
550 | |
727 | |
551 | 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. |
552 | |
729 | |
553 | =back |
730 | =back |
|
|
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 | |
554 | |
752 | |
555 | =head1 THREADS |
753 | =head1 THREADS |
556 | |
754 | |
557 | Threads are not supported by this module in any way. Perl pseudo-threads |
755 | Threads are not supported by this module in any way. Perl pseudo-threads |
558 | is evil stuff and must die. As soon as Perl gains real threads I will work |
756 | is evil stuff and must die. As soon as Perl gains real threads I will work |
… | |
… | |
586 | |
784 | |
587 | 1; |
785 | 1; |
588 | |
786 | |
589 | =head1 SEE ALSO |
787 | =head1 SEE ALSO |
590 | |
788 | |
591 | L<EV::DNS>. |
789 | L<EV::DNS>. |
592 | |
790 | |
593 | =head1 AUTHOR |
791 | =head1 AUTHOR |
594 | |
792 | |
595 | Marc Lehmann <schmorp@schmorp.de> |
793 | Marc Lehmann <schmorp@schmorp.de> |
596 | http://home.schmorp.de/ |
794 | http://home.schmorp.de/ |