ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/EV.pm
(Generate patch)

Comparing EV/EV.pm (file contents):
Revision 1.40 by root, Fri Nov 16 05:04:36 2007 UTC vs.
Revision 1.75 by root, Fri Dec 21 10:36:22 2007 UTC

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
52This module provides an interface to libev 58This 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
60below is comprehensive, one might also consult the documentation of libev
61itself (L<http://cvs.schmorp.de/libev/ev.html>) for more subtle details on
62watcher semantics or some discussion on the available backends, or how to
63force a specific backend with C<LIBEV_FLAGS>, or just about in any case
64because it has much more detailed information.
54 65
55=cut 66=cut
56 67
57package EV; 68package EV;
58 69
59use strict; 70use strict;
60 71
61BEGIN { 72BEGIN {
62 our $VERSION = '0.9'; 73 our $VERSION = '2.0';
63 use XSLoader; 74 use XSLoader;
64 XSLoader::load "EV", $VERSION; 75 XSLoader::load "EV", $VERSION;
65} 76}
66 77
67@EV::Io::ISA = 78@EV::IO::ISA =
68@EV::Timer::ISA = 79@EV::Timer::ISA =
69@EV::Periodic::ISA = 80@EV::Periodic::ISA =
70@EV::Signal::ISA = 81@EV::Signal::ISA =
82@EV::Child::ISA =
83@EV::Stat::ISA =
71@EV::Idle::ISA = 84@EV::Idle::ISA =
72@EV::Prepare::ISA = 85@EV::Prepare::ISA =
73@EV::Check::ISA = 86@EV::Check::ISA =
74@EV::Child::ISA = "EV::Watcher"; 87@EV::Embed::ISA =
88@EV::Fork::ISA =
89 "EV::Watcher";
90
91@EV::Loop::Default::ISA = "EV::Loop";
92
93=head1 EVENT LOOPS
94
95EV supports multiple event loops: There is a single "default event loop"
96that can handle everything including signals and child watchers, and any
97number of "dynamic event loops" that can use different backends (with
98various limitations), but no child and signal watchers.
99
100You do not have to do anything to create the default event loop: When
101the module is loaded a suitable backend is selected on the premise of
102selecting a working backend (which for example rules out kqueue on most
103BSDs). Modules should, unless they have "special needs" always use the
104default loop as this is fastest (perl-wise), best supported by other
105modules (e.g. AnyEvent or Coro) and most portable event loop.
106
107For specific programs you cna create additional event loops dynamically.
108
109=over 4
110
111=item $loop = new EV::loop [$flags]
112
113Create a new event loop as per the specified flags. Please refer to the
114C<ev_loop_new ()> function description in the libev documentation
115(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>)
116for more info.
117
118The loop will automatically be destroyed when it is no longer referenced
119by any watcher and the loop object goes out of scope.
120
121Using C<EV::FLAG_FORKCHECK> is recommended, as only the default event loop
122is protected by this module.
123
124=item $loop->loop_fork
125
126Must be called after a fork in the child, before entering or continuing
127the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
128this fucntion automatically, at some performance loss (refer to the libev
129documentation).
130
131=back
132
75 133
76=head1 BASIC INTERFACE 134=head1 BASIC INTERFACE
77 135
78=over 4 136=over 4
79 137
80=item $EV::DIED 138=item $EV::DIED
81 139
82Must contain a reference to a function that is called when a callback 140Must contain a reference to a function that is called when a callback
83throws an exception (with $@ containing thr error). The default prints an 141throws an exception (with $@ containing the error). The default prints an
84informative message and continues. 142informative message and continues.
85 143
86If this callback throws an exception it will be silently ignored. 144If this callback throws an exception it will be silently ignored.
87 145
88=item $time = EV::time 146=item $time = EV::time
89 147
90Returns the current time in (fractional) seconds since the epoch. 148Returns the current time in (fractional) seconds since the epoch.
91 149
92=item $time = EV::now 150=item $time = EV::now
151
152=item $time = $loop->now
93 153
94Returns the time the last event loop iteration has been started. This 154Returns the time the last event loop iteration has been started. This
95is the time that (relative) timers are based on, and refering to it is 155is the time that (relative) timers are based on, and refering to it is
96usually faster then calling EV::time. 156usually faster then calling EV::time.
97 157
98=item $method = EV::ev_method 158=item $backend = EV::backend
159
160=item $backend = $loop->backend
99 161
100Returns an integer describing the backend used by libev (EV::METHOD_SELECT 162Returns an integer describing the backend used by libev (EV::METHOD_SELECT
101or EV::METHOD_EPOLL). 163or EV::METHOD_EPOLL).
102 164
103=item EV::loop [$flags] 165=item EV::loop [$flags]
166
167=item $loop->loop ([$flags])
104 168
105Begin checking for events and calling callbacks. It returns when a 169Begin checking for events and calling callbacks. It returns when a
106callback calls EV::unloop. 170callback calls EV::unloop.
107 171
108The $flags argument can be one of the following: 172The $flags argument can be one of the following:
111 EV::LOOP_ONESHOT block at most once (wait, but do not loop) 175 EV::LOOP_ONESHOT block at most once (wait, but do not loop)
112 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) 176 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)
113 177
114=item EV::unloop [$how] 178=item EV::unloop [$how]
115 179
180=item $loop->unloop ([$how])
181
116When called with no arguments or an argument of EV::UNLOOP_ONE, makes the 182When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
117innermost call to EV::loop return. 183innermost call to EV::loop return.
118 184
119When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as 185When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
120fast as possible. 186fast as possible.
121 187
122=back 188=item $count = EV::loop_count
123 189
124=head2 WATCHER 190=item $count = $loop->loop_count
191
192Return the number of times the event loop has polled for new
193events. Sometiems useful as a generation counter.
194
195=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
196
197=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
198
199This function rolls together an I/O and a timer watcher for a single
200one-shot event without the need for managing a watcher object.
201
202If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
203must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
204| EV::WRITE>, indicating the type of I/O event you want to wait for. If
205you do not want to wait for some I/O event, specify C<undef> for
206C<$fh_or_undef> and C<0> for C<$events>).
207
208If timeout is C<undef> or negative, then there will be no
209timeout. Otherwise a EV::timer with this value will be started.
210
211When an error occurs or either the timeout or I/O watcher triggers, then
212the callback will be called with the received event set (in general
213you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>,
214C<EV::WRITE> and C<EV::TIMEOUT>).
215
216EV::once doesn't return anything: the watchers stay active till either
217of them triggers, then they will be stopped and freed, and the callback
218invoked.
219
220=item EV::feed_fd_event ($fd, $revents)
221
222=item $loop->feed_fd_event ($fd, $revents)
223
224Feed an event on a file descriptor into EV. EV will react to this call as
225if the readyness notifications specified by C<$revents> (a combination of
226C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
227
228=item EV::feed_signal_event ($signal)
229
230Feed a signal event into EV. EV will react to this call as if the signal
231specified by C<$signal> had occured.
232
233=back
234
235
236=head1 WATCHER OBJECTS
125 237
126A watcher is an object that gets created to record your interest in some 238A watcher is an object that gets created to record your interest in some
127event. For instance, if you want to wait for STDIN to become readable, you 239event. For instance, if you want to wait for STDIN to become readable, you
128would create an EV::io watcher for that: 240would create an EV::io watcher for that:
129 241
138events. 250events.
139 251
140Each watcher type has its associated bit in revents, so you can use the 252Each watcher type has its associated bit in revents, so you can use the
141same callback for multiple watchers. The event mask is named after the 253same callback for multiple watchers. The event mask is named after the
142type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, 254type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
143EV::periodic sets EV::PERIODIC and so on, with the exception of IO events 255EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
144(which can set both EV::READ and EV::WRITE bits), and EV::timer (which 256(which can set both EV::READ and EV::WRITE bits), and EV::timer (which
145uses EV::TIMEOUT). 257uses EV::TIMEOUT).
146 258
147In the rare case where one wants to create a watcher but not start it at 259In the rare case where one wants to create a watcher but not start it at
148the same time, each constructor has a variant with a trailing C<_ns> in 260the same time, each constructor has a variant with a trailing C<_ns> in
154 266
155Also, all methods changing some aspect of a watcher (->set, ->priority, 267Also, 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, 268->fh and so on) automatically stop and start it again if it is active,
157which means pending events get lost. 269which means pending events get lost.
158 270
159=head2 WATCHER TYPES 271=head2 COMMON WATCHER METHODS
160 272
161Now lets move to the existing watcher types and asociated methods. 273This section lists methods common to all watchers.
162
163The following methods are available for all watchers. Then followes a
164description of each watcher constructor (EV::io, EV::timer, EV::periodic,
165EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by
166any type-specific methods (if any).
167 274
168=over 4 275=over 4
169 276
170=item $w->start 277=item $w->start
171 278
175 282
176=item $w->stop 283=item $w->stop
177 284
178Stop a watcher if it is active. Also clear any pending events (events that 285Stop a watcher if it is active. Also clear any pending events (events that
179have been received but that didn't yet result in a callback invocation), 286have been received but that didn't yet result in a callback invocation),
180regardless of wether the watcher was active or not. 287regardless of whether the watcher was active or not.
181 288
182=item $bool = $w->is_active 289=item $bool = $w->is_active
183 290
184Returns true if the watcher is active, false otherwise. 291Returns true if the watcher is active, false otherwise.
185 292
210watchers with higher priority will be invoked first. The valid range of 317watchers with higher priority will be invoked first. The valid range of
211priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default 318priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
212-2). If the priority is outside this range it will automatically be 319-2). If the priority is outside this range it will automatically be
213normalised to the nearest valid priority. 320normalised to the nearest valid priority.
214 321
215The default priority of any newly-created weatcher is 0. 322The default priority of any newly-created watcher is 0.
216 323
324Note that the priority semantics have not yet been fleshed out and are
325subject to almost certain change.
326
217=item $w->trigger ($revents) 327=item $w->invoke ($revents)
218 328
219Call the callback *now* with the given event mask. 329Call the callback *now* with the given event mask.
220 330
331=item $w->feed_event ($revents)
332
333Feed some events on this watcher into EV. EV will react to this call as if
334the watcher had received the given C<$revents> mask.
335
336=item $revents = $w->clear_pending
337
338If the watcher is pending, this function returns clears its pending status
339and returns its C<$revents> bitset (as if its callback was invoked). If the
340watcher isn't pending it does nothing and returns C<0>.
341
342=item $previous_state = $w->keepalive ($bool)
343
344Normally, C<EV::loop> will return when there are no active watchers
345(which is a "deadlock" because no progress can be made anymore). This is
346convinient because it allows you to start your watchers (and your jobs),
347call C<EV::loop> once and when it returns you know that all your jobs are
348finished (or they forgot to register some watchers for their task :).
349
350Sometimes, however, this gets in your way, for example when you the module
351that calls C<EV::loop> (usually the main program) is not the same module
352as a long-living watcher (for example a DNS client module written by
353somebody else even). Then you might want any outstanding requests to be
354handled, but you would not want to keep C<EV::loop> from returning just
355because you happen to have this long-running UDP port watcher.
356
357In this case you can clear the keepalive status, which means that even
358though your watcher is active, it won't keep C<EV::loop> from returning.
359
360The initial value for keepalive is true (enabled), and you cna change it
361any time.
362
363Example: Register an I/O watcher for some UDP socket but do not keep the
364event loop from running just because of that watcher.
365
366 my $udp_socket = ...
367 my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... };
368 $1000udp_watcher->keepalive (0);
369
370=item $loop = $w->loop
371
372Return the loop that this watcher is attached to.
373
374=back
375
376
377=head1 WATCHER TYPES
378
379Each of the following subsections describes a single watcher type.
380
381=head3 I/O WATCHERS - is this file descriptor readable or writable?
382
383=over 4
221 384
222=item $w = EV::io $fileno_or_fh, $eventmask, $callback 385=item $w = EV::io $fileno_or_fh, $eventmask, $callback
223 386
224=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 387=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
225 388
389=item $w = $loop->io 8$fileno_or_fh, $eventmask, $callback)
390
391=item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback)
392
226As long as the returned watcher object is alive, call the C<$callback> 393As long as the returned watcher object is alive, call the C<$callback>
227when the events specified in C<$eventmask>. 394when at least one of events specified in C<$eventmask> occurs.
228 395
229The $eventmask can be one or more of these constants ORed together: 396The $eventmask can be one or more of these constants ORed together:
230 397
231 EV::READ wait until read() wouldn't block anymore 398 EV::READ wait until read() wouldn't block anymore
232 EV::WRITE wait until write() wouldn't block anymore 399 EV::WRITE wait until write() wouldn't block anymore
248 415
249=item $old_eventmask = $w->events ($new_eventmask) 416=item $old_eventmask = $w->events ($new_eventmask)
250 417
251Returns the previously set event mask and optionally set a new one. 418Returns the previously set event mask and optionally set a new one.
252 419
420=back
421
422
423=head3 TIMER WATCHERS - relative and optionally repeating timeouts
424
425=over 4
253 426
254=item $w = EV::timer $after, $repeat, $callback 427=item $w = EV::timer $after, $repeat, $callback
255 428
256=item $w = EV::timer_ns $after, $repeat, $callback 429=item $w = EV::timer_ns $after, $repeat, $callback
257 430
258Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 431=item $w = $loop->timer ($after, $repeat, $callback)
259the timer will be restarted (with the $repeat value as $after) after the 432
260callback returns. 433=item $w = $loop->timer_ns ($after, $repeat, $callback)
434
435Calls the callback after C<$after> seconds (which may be fractional). If
436C<$repeat> is non-zero, the timer will be restarted (with the $repeat
437value as $after) after the callback returns.
261 438
262This means that the callback would be called roughly after C<$after> 439This means that the callback would be called roughly after C<$after>
263seconds, and then every C<$repeat> seconds. The timer does his best not 440seconds, and then every C<$repeat> seconds. The timer does his best not
264to drift, but it will not invoke the timer more often then once per event 441to drift, but it will not invoke the timer more often then once per event
265loop iteration, and might drift in other cases. If that isn't acceptable, 442loop iteration, and might drift in other cases. If that isn't acceptable,
271 448
272The C<timer_ns> variant doesn't start (activate) the newly created watcher. 449The C<timer_ns> variant doesn't start (activate) the newly created watcher.
273 450
274=item $w->set ($after, $repeat) 451=item $w->set ($after, $repeat)
275 452
276Reconfigures the watcher, see the constructor above for details. Can be at 453Reconfigures the watcher, see the constructor above for details. Can be called at
277any time. 454any time.
278 455
279=item $w->again 456=item $w->again
280 457
281Similar to the C<start> method, but has special semantics for repeating timers: 458Similar to the C<start> method, but has special semantics for repeating timers:
292This behaviour is useful when you have a timeout for some IO 469This behaviour is useful when you have a timeout for some IO
293operation. You create a timer object with the same value for C<$after> and 470operation. You create a timer object with the same value for C<$after> and
294C<$repeat>, and then, in the read/write watcher, run the C<again> method 471C<$repeat>, and then, in the read/write watcher, run the C<again> method
295on the timeout. 472on the timeout.
296 473
474=back
475
476
477=head3 PERIODIC WATCHERS - to cron or not to cron?
478
479=over 4
297 480
298=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback 481=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
299 482
300=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback 483=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
484
485=item $w = $loop->periodic ($at, $interval, $reschedule_cb, $callback)
486
487=item $w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback)
301 488
302Similar to EV::timer, but is not based on relative timeouts but on 489Similar to EV::timer, but is not based on relative timeouts but on
303absolute times. Apart from creating "simple" timers that trigger "at" the 490absolute times. Apart from creating "simple" timers that trigger "at" the
304specified time, it can also be used for non-drifting absolute timers and 491specified time, it can also be used for non-drifting absolute timers and
305more complex, cron-like, setups that are not adversely affected by time 492more complex, cron-like, setups that are not adversely affected by time
373 560
374The C<periodic_ns> variant doesn't start (activate) the newly created watcher. 561The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
375 562
376=item $w->set ($at, $interval, $reschedule_cb) 563=item $w->set ($at, $interval, $reschedule_cb)
377 564
378Reconfigures the watcher, see the constructor above for details. Can be at 565Reconfigures the watcher, see the constructor above for details. Can be called at
379any time. 566any time.
380 567
381=item $w->again 568=item $w->again
382 569
383Simply stops and starts the watcher again. 570Simply stops and starts the watcher again.
384 571
572=item $time = $w->at
573
574Return the time that the watcher is expected to trigger next.
575
576=back
577
578
579=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
580
581=over 4
385 582
386=item $w = EV::signal $signal, $callback 583=item $w = EV::signal $signal, $callback
387 584
388=item $w = EV::signal_ns $signal, $callback 585=item $w = EV::signal_ns $signal, $callback
389 586
390Call the callback when $signal is received (the signal can be specified 587Call the callback when $signal is received (the signal can be specified by
391by number or by name, just as with kill or %SIG). 588number or by name, just as with C<kill> or C<%SIG>).
392 589
393EV will grab the signal for the process (the kernel only allows one 590EV will grab the signal for the process (the kernel only allows one
394component to receive a signal at a time) when you start a signal watcher, 591component to receive a signal at a time) when you start a signal watcher,
395and removes it again when you stop it. Perl does the same when you 592and removes it again when you stop it. Perl does the same when you
396add/remove callbacks to %SIG, so watch out. 593add/remove callbacks to C<%SIG>, so watch out.
397 594
398You can have as many signal watchers per signal as you want. 595You can have as many signal watchers per signal as you want.
399 596
400The C<signal_ns> variant doesn't start (activate) the newly created watcher. 597The C<signal_ns> variant doesn't start (activate) the newly created watcher.
401 598
402=item $w->set ($signal) 599=item $w->set ($signal)
403 600
404Reconfigures the watcher, see the constructor above for details. Can be at 601Reconfigures the watcher, see the constructor above for details. Can be
405any time. 602called at any time.
406 603
407=item $current_signum = $w->signal 604=item $current_signum = $w->signal
408 605
409=item $old_signum = $w->signal ($new_signal) 606=item $old_signum = $w->signal ($new_signal)
410 607
411Returns the previously set signal (always as a number not name) and 608Returns the previously set signal (always as a number not name) and
412optionally set a new one. 609optionally set a new one.
413 610
611=back
612
613
614=head3 CHILD WATCHERS - watch out for process status changes
615
616=over 4
414 617
415=item $w = EV::child $pid, $callback 618=item $w = EV::child $pid, $callback
416 619
417=item $w = EV::child_ns $pid, $callback 620=item $w = EV::child_ns $pid, $callback
418 621
622=item $w = $loop->child ($pid, $callback)
623
624=item $w = $loop->child_ns ($pid, $callback)
625
419Call the callback when a status change for pid C<$pid> (or any pid 626Call the callback when a status change for pid C<$pid> (or any pid if
420if C<$pid> is 0) has been received. More precisely: when the process 627C<$pid> is 0) has been received. More precisely: when the process receives
421receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all 628a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
422changed/zombie children and call the callback. 629changed/zombie children and call the callback.
423 630
424You can access both status and pid by using the C<rstatus> and C<rpid> 631It is valid (and fully supported) to install a child watcher after a child
425methods on the watcher object. 632has exited but before the event loop has started its next iteration (for
633example, first you C<fork>, then the new child process might exit, and
634only then do you install a child watcher in the parent for the new pid).
426 635
636You can access both exit (or tracing) status and pid by using the
637C<rstatus> and C<rpid> methods on the watcher object.
638
427You can have as many pid watchers per pid as you want. 639You can have as many pid watchers per pid as you want, they will all be
640called.
428 641
429The C<child_ns> variant doesn't start (activate) the newly created watcher. 642The C<child_ns> variant doesn't start (activate) the newly created watcher.
430 643
431=item $w->set ($pid) 644=item $w->set ($pid)
432 645
433Reconfigures the watcher, see the constructor above for details. Can be at 646Reconfigures the watcher, see the constructor above for details. Can be called at
434any time. 647any time.
435 648
436=item $current_pid = $w->pid 649=item $current_pid = $w->pid
437 650
438=item $old_pid = $w->pid ($new_pid) 651=item $old_pid = $w->pid ($new_pid)
447=item $pid = $w->rpid 660=item $pid = $w->rpid
448 661
449Return the pid of the awaited child (useful when you have installed a 662Return the pid of the awaited child (useful when you have installed a
450watcher for all pids). 663watcher for all pids).
451 664
665=back
666
667
668=head3 STAT WATCHERS - did the file attributes just change?
669
670=over 4
671
672=item $w = EV::stat $path, $interval, $callback
673
674=item $w = EV::stat_ns $path, $interval, $callback
675
676=item $w = $loop->stat ($path, $interval, $callback)
677
678=item $w = $loop->stat_ns ($path, $interval, $callback)
679
680Call the callback when a file status change has been detected on
681C<$path>. The C<$path> does not need to exist, changing from "path exists"
682to "path does not exist" is a status change like any other.
683
684The C<$interval> is a recommended polling interval for systems where
685OS-supported change notifications don't exist or are not supported. If
686you use C<0> then an unspecified default is used (which is highly
687recommended!), which is to be expected to be around five seconds usually.
688
689This watcher type is not meant for massive numbers of stat watchers,
690as even with OS-supported change notifications, this can be
691resource-intensive.
692
693The C<stat_ns> variant doesn't start (activate) the newly created watcher.
694
695=item ... = $w->stat
696
697This call is very similar to the perl C<stat> built-in: It stats (using
698C<lstat>) the path specified in the watcher and sets perls stat cache (as
699well as EV's idea of the current stat values) to the values found.
700
701In scalar context, a boolean is return indicating success or failure of
702the stat. In list context, the same 13-value list as with stat is returned
703(except that the blksize and blocks fields are not reliable).
704
705In the case of an error, errno is set to C<ENOENT> (regardless of the
706actual error value) and the C<nlink> value is forced to zero (if the stat
707was successful then nlink is guaranteed to be non-zero).
708
709See also the next two entries for more info.
710
711=item ... = $w->attr
712
713Just like C<< $w->stat >>, but without the initial stat'ing: this returns
714the values most recently detected by EV. See the next entry for more info.
715
716=item ... = $w->prev
717
718Just like C<< $w->stat >>, but without the initial stat'ing: this returns
719the previous set of values, before the change.
720
721That is, when the watcher callback is invoked, C<< $w->prev >> will be set
722to the values found I<before> a change was detected, while C<< $w->attr >>
723returns the values found leading to the change detection. The difference (if any)
724between C<prev> and C<attr> is what triggered the callback.
725
726If you did something to the filesystem object and do not want to trigger
727yet another change, you can call C<stat> to update EV's idea of what the
728current attributes are.
729
730=item $w->set ($path, $interval)
731
732Reconfigures the watcher, see the constructor above for details. Can be
733called at any time.
734
735=item $current_path = $w->path
736
737=item $old_path = $w->path ($new_path)
738
739Returns the previously set path and optionally set a new one.
740
741=item $current_interval = $w->interval
742
743=item $old_interval = $w->interval ($new_interval)
744
745Returns the previously set interval and optionally set a new one. Can be
746used to query the actual interval used.
747
748=back
749
750
751=head3 IDLE WATCHERS - when you've got nothing better to do...
752
753=over 4
452 754
453=item $w = EV::idle $callback 755=item $w = EV::idle $callback
454 756
455=item $w = EV::idle_ns $callback 757=item $w = EV::idle_ns $callback
456 758
457Call the callback when there are no pending io, timer/periodic, signal or 759=item $w = $loop->idle ($callback)
458child events, i.e. when the process is idle. 760
761=item $w = $loop->idle_ns ($callback)
762
763Call the callback when there are no other pending watchers of the same or
764higher priority (excluding check, prepare and other idle watchers of the
765same or lower priority, of course). They are called idle watchers because
766when the watcher is the highest priority pending event in the process, the
767process is considered to be idle at that priority.
768
769If you want a watcher that is only ever called when I<no> other events are
770outstanding you have to set the priority to C<EV::MINPRI>.
459 771
460The process will not block as long as any idle watchers are active, and 772The process will not block as long as any idle watchers are active, and
461they will be called repeatedly until stopped. 773they will be called repeatedly until stopped.
462 774
775For example, if you have idle watchers at priority C<0> and C<1>, and
776an I/O watcher at priority C<0>, then the idle watcher at priority C<1>
777and the I/O watcher will always run when ready. Only when the idle watcher
778at priority C<1> is stopped and the I/O watcher at priority C<0> is not
779pending with the C<0>-priority idle watcher be invoked.
780
463The C<idle_ns> variant doesn't start (activate) the newly created watcher. 781The C<idle_ns> variant doesn't start (activate) the newly created watcher.
464 782
783=back
784
785
786=head3 PREPARE WATCHERS - customise your event loop!
787
788=over 4
465 789
466=item $w = EV::prepare $callback 790=item $w = EV::prepare $callback
467 791
468=item $w = EV::prepare_ns $callback 792=item $w = EV::prepare_ns $callback
793
794=item $w = $loop->prepare ($callback)
795
796=item $w = $loop->prepare_ns 8$callback)
469 797
470Call the callback just before the process would block. You can still 798Call the callback just before the process would block. You can still
471create/modify any watchers at this point. 799create/modify any watchers at this point.
472 800
473See the EV::check watcher, below, for explanations and an example. 801See the EV::check watcher, below, for explanations and an example.
474 802
475The C<prepare_ns> variant doesn't start (activate) the newly created watcher. 803The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
476 804
805=back
806
807
808=head3 CHECK WATCHERS - customise your event loop even more!
809
810=over 4
477 811
478=item $w = EV::check $callback 812=item $w = EV::check $callback
479 813
480=item $w = EV::check_ns $callback 814=item $w = EV::check_ns $callback
815
816=item $w = $loop->check ($callback)
817
818=item $w = $loop->check_ns ($callback)
481 819
482Call the callback just after the process wakes up again (after it has 820Call the callback just after the process wakes up again (after it has
483gathered events), but before any other callbacks have been invoked. 821gathered events), but before any other callbacks have been invoked.
484 822
485This is used to integrate other event-based software into the EV 823This is used to integrate other event-based software into the EV
493 # do nothing unless active 831 # do nothing unless active
494 $dispatcher->{_event_queue_h} 832 $dispatcher->{_event_queue_h}
495 or return; 833 or return;
496 834
497 # make the dispatcher handle any outstanding stuff 835 # make the dispatcher handle any outstanding stuff
836 ... not shown
498 837
499 # create an IO watcher for each and every socket 838 # create an I/O watcher for each and every socket
500 @snmp_watcher = ( 839 @snmp_watcher = (
501 (map { EV::io $_, EV::READ, sub { } } 840 (map { EV::io $_, EV::READ, sub { } }
502 keys %{ $dispatcher->{_descriptors} }), 841 keys %{ $dispatcher->{_descriptors} }),
842
843 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
844 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
845 0, sub { },
503 ); 846 );
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 }; 847 };
509 848
510The callbacks are irrelevant, the only purpose of those watchers is 849The callbacks are irrelevant (and are not even being called), the
511to wake up the process as soon as one of those events occurs (socket 850only purpose of those watchers is to wake up the process as soon as
512readable, or timer timed out). The corresponding EV::check watcher will then 851one of those events occurs (socket readable, or timer timed out). The
513clean up: 852corresponding EV::check watcher will then clean up:
514 853
515 our $snmp_check = EV::check sub { 854 our $snmp_check = EV::check sub {
516 # destroy all watchers 855 # destroy all watchers
517 @snmp_watcher = (); 856 @snmp_watcher = ();
518 857
519 # make the dispatcher handle any new stuff 858 # make the dispatcher handle any new stuff
859 ... not shown
520 }; 860 };
521 861
522The callbacks of the created watchers will not be called as the watchers 862The callbacks of the created watchers will not be called as the watchers
523are destroyed before this cna happen (remember EV::check gets called 863are destroyed before this cna happen (remember EV::check gets called
524first). 864first).
525 865
526The C<check_ns> variant doesn't start (activate) the newly created watcher. 866The C<check_ns> variant doesn't start (activate) the newly created watcher.
527 867
528=back 868=back
529 869
870
871=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
872
873Fork watchers are called when a C<fork ()> was detected. The invocation
874is done before the event loop blocks next and before C<check> watchers
875are being called, and only in the child after the fork.
876
877=over 4
878
879=item $w = EV::fork $callback
880
881=item $w = EV::fork_ns $callback
882
883=item $w = $loop->fork ($callback)
884
885=item $w = $loop->fork_ns ($callback)
886
887Call the callback before the event loop is resumed in the child process
888after a fork.
889
890The C<fork_ns> variant doesn't start (activate) the newly created watcher.
891
892=back
893
894
895=head1 PERL SIGNALS
896
897While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
898with EV is as the same as any other C library: Perl-signals will only be
899handled when Perl runs, which means your signal handler might be invoked
900only the next time an event callback is invoked.
901
902The solution is to use EV signal watchers (see C<EV::signal>), which will
903ensure proper operations with regards to other event watchers.
904
905If you cannot do this for whatever reason, you can also force a watcher
906to be called on every event loop iteration by installing a C<EV::check>
907watcher:
908
909 my $async_check = EV::check sub { };
910
911This ensures that perl gets into control for a short time to handle any
912pending signals, and also ensures (slightly) slower overall operation.
913
530=head1 THREADS 914=head1 THREADS
531 915
532Threads are not supported by this in any way. Perl pseudo-threads is evil 916Threads are not supported by this module in any way. Perl pseudo-threads
533stuff and must die. 917is evil stuff and must die. As soon as Perl gains real threads I will work
918on thread support for it.
919
920=head1 FORK
921
922Most of the "improved" event delivering mechanisms of modern operating
923systems have quite a few problems with fork(2) (to put it bluntly: it is
924not supported and usually destructive). Libev makes it possible to work
925around this by having a function that recreates the kernel state after
926fork in the child.
927
928On non-win32 platforms, this module requires the pthread_atfork
929functionality to do this automatically for you. This function is quite
930buggy on most BSDs, though, so YMMV. The overhead for this is quite
931negligible, because everything the function currently does is set a flag
932that is checked only when the event loop gets used the next time, so when
933you do fork but not use EV, the overhead is minimal.
934
935On win32, there is no notion of fork so all this doesn't apply, of course.
534 936
535=cut 937=cut
536 938
537our $DIED = sub { 939our $DIED = sub {
538 warn "EV: error in callback (ignoring): $@"; 940 warn "EV: error in callback (ignoring): $@";
539}; 941};
540 942
541default_loop 943default_loop
542 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?'; 944 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_FLAGS}?';
543 945
5441; 9461;
545 947
546=head1 SEE ALSO 948=head1 SEE ALSO
547 949
548 L<EV::DNS>. 950L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as
951event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient
952coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP).
549 953
550=head1 AUTHOR 954=head1 AUTHOR
551 955
552 Marc Lehmann <schmorp@schmorp.de> 956 Marc Lehmann <schmorp@schmorp.de>
553 http://home.schmorp.de/ 957 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines