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

Comparing EV/EV.pm (file contents):
Revision 1.24 by root, Fri Nov 2 22:03:00 2007 UTC vs.
Revision 1.61 by root, Thu Dec 6 03:13:07 2007 UTC

10 10
11 my $w = EV::timer 2, 0, sub { 11 my $w = EV::timer 2, 0, sub {
12 warn "is called after 2s"; 12 warn "is called after 2s";
13 }; 13 };
14 14
15 my $w = EV::timer 2, 1, sub { 15 my $w = EV::timer 2, 2, sub {
16 warn "is called roughly every 2s (repeat = 1)"; 16 warn "is called roughly every 2s (repeat = 2)";
17 }; 17 };
18 18
19 undef $w; # destroy event watcher again 19 undef $w; # destroy event watcher again
20 20
21 my $w = EV::periodic 0, 60, sub { 21 my $w = EV::periodic 0, 60, 0, sub {
22 warn "is called every minute, on the minute, exactly"; 22 warn "is called every minute, on the minute, exactly";
23 }; 23 };
24 24
25 # IO 25 # IO
26 26
27 my $w = EV::io *STDIN, EV::READ, sub { 27 my $w = EV::io *STDIN, EV::READ, sub {
28 my ($w, $revents) = @_; # all callbacks get the watcher object and event mask 28 my ($w, $revents) = @_; # all callbacks receive the watcher and event mask
29 warn "stdin is readable, you entered: ", <STDIN>; 29 warn "stdin is readable, you entered: ", <STDIN>;
30 }; 30 };
31 31
32 # SIGNALS 32 # SIGNALS
33 33
34 my $w = EV::signal 'QUIT', sub { 34 my $w = EV::signal 'QUIT', sub {
35 warn "sigquit received\n"; 35 warn "sigquit received\n";
36 }; 36 };
37 37
38 # CHILD/PID STATUS CHANGES
39
38 my $w = EV::signal 3, sub { 40 my $w = EV::child 666, sub {
39 warn "sigquit received (this is GNU/Linux, right?)\n"; 41 my ($w, $revents) = @_;
42 my $status = $w->rstatus;
40 }; 43 };
41 44
42 # CHILD/PID STATUS CHANGES 45 # STAT CHANGES
43 46 my $w = EV::stat "/etc/passwd", 10, sub {
44 my $w = EV::child 666, sub {
45 my ($w, $revents, $status) = @_; 47 my ($w, $revents) = @_;
48 warn $w->path, " has changed somehow.\n";
46 }; 49 };
47 50
48 # MAINLOOP 51 # MAINLOOP
49 EV::loop; # loop until EV::loop_done is called 52 EV::loop; # loop until EV::unloop is called or all watchers stop
50 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
51 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
52 55
53=head1 DESCRIPTION 56=head1 DESCRIPTION
54 57
55This module provides an interface to libev 58This module provides an interface to libev
56(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>.
57 64
58=cut 65=cut
59 66
60package EV; 67package EV;
61 68
62use strict; 69use strict;
63 70
64BEGIN { 71BEGIN {
65 our $VERSION = '0.1'; 72 our $VERSION = '1.6';
66 use XSLoader; 73 use XSLoader;
67 XSLoader::load "EV", $VERSION; 74 XSLoader::load "EV", $VERSION;
68} 75}
69 76
70@EV::Io::ISA = 77@EV::IO::ISA =
71@EV::Timer::ISA = 78@EV::Timer::ISA =
72@EV::Periodic::ISA = 79@EV::Periodic::ISA =
73@EV::Signal::ISA = 80@EV::Signal::ISA =
81@EV::Child::ISA =
82@EV::Stat::ISA =
74@EV::Idle::ISA = 83@EV::Idle::ISA =
75@EV::Prepare::ISA = 84@EV::Prepare::ISA =
76@EV::Check::ISA = 85@EV::Check::ISA =
77@EV::Child::ISA = "EV::Watcher"; 86@EV::Embed::ISA =
87@EV::Fork::ISA =
88 "EV::Watcher";
78 89
79=head1 BASIC INTERFACE 90=head1 BASIC INTERFACE
80 91
81=over 4 92=over 4
82 93
96 107
97Returns the time the last event loop iteration has been started. This 108Returns the time the last event loop iteration has been started. This
98is the time that (relative) timers are based on, and refering to it is 109is the time that (relative) timers are based on, and refering to it is
99usually faster then calling EV::time. 110usually faster then calling EV::time.
100 111
101=item $method = EV::ev_method 112=item $method = EV::method
102 113
103Returns an integer describing the backend used by libev (EV::METHOD_SELECT 114Returns an integer describing the backend used by libev (EV::METHOD_SELECT
104or EV::METHOD_EPOLL). 115or EV::METHOD_EPOLL).
105 116
106=item EV::loop [$flags] 117=item EV::loop [$flags]
107 118
108Begin checking for events and calling callbacks. It returns when a 119Begin checking for events and calling callbacks. It returns when a
109callback calls EV::loop_done. 120callback calls EV::unloop.
110 121
111The $flags argument can be one of the following: 122The $flags argument can be one of the following:
112 123
113 0 as above 124 0 as above
114 EV::LOOP_ONESHOT block at most once (wait, but do not loop) 125 EV::LOOP_ONESHOT block at most once (wait, but do not loop)
115 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) 126 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)
116 127
117=item EV::loop_done [$how] 128=item EV::unloop [$how]
118 129
119When called with no arguments or an argument of 1, makes the innermost 130When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
120call to EV::loop return. 131innermost call to EV::loop return.
121 132
122When called with an agrument of 2, all calls to EV::loop will return as 133When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
123fast as possible. 134fast as possible.
124 135
125=back 136=item $count = EV::loop_count
126 137
138Return the number of times the event loop has polled for new
139events. Sometiems useful as a generation counter.
140
141=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
142
143This function rolls together an I/O and a timer watcher for a single
144one-shot event without the need for managing a watcher object.
145
146If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
147must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
148| EV::WRITE>, indicating the type of I/O event you want to wait for. If
149you do not want to wait for some I/O event, specify C<undef> for
150C<$fh_or_undef> and C<0> for C<$events>).
151
152If timeout is C<undef> or negative, then there will be no
153timeout. Otherwise a EV::timer with this value will be started.
154
155When an error occurs or either the timeout or I/O watcher triggers, then
156the callback will be called with the received event set (in general
157you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>,
158C<EV::WRITE> and C<EV::TIMEOUT>).
159
160EV::once doesn't return anything: the watchers stay active till either
161of them triggers, then they will be stopped and freed, and the callback
162invoked.
163
164=back
165
127=head2 WATCHER 166=head2 WATCHER OBJECTS
128 167
129A watcher is an object that gets created to record your interest in some 168A watcher is an object that gets created to record your interest in some
130event. For instance, if you want to wait for STDIN to become readable, you 169event. For instance, if you want to wait for STDIN to become readable, you
131would create an EV::io watcher for that: 170would create an EV::io watcher for that:
132 171
157 196
158Also, all methods changing some aspect of a watcher (->set, ->priority, 197Also, all methods changing some aspect of a watcher (->set, ->priority,
159->fh and so on) automatically stop and start it again if it is active, 198->fh and so on) automatically stop and start it again if it is active,
160which means pending events get lost. 199which means pending events get lost.
161 200
162=head2 WATCHER TYPES 201=head2 COMMON WATCHER METHODS
163 202
164Now lets move to the existing watcher types and asociated methods. 203This section lists methods common to all watchers.
165
166The following methods are available for all watchers. Then followes a
167description of each watcher constructor (EV::io, EV::timer, EV::periodic,
168EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by
169any type-specific methods (if any).
170 204
171=over 4 205=over 4
172 206
173=item $w->start 207=item $w->start
174 208
183regardless of wether the watcher was active or not. 217regardless of wether the watcher was active or not.
184 218
185=item $bool = $w->is_active 219=item $bool = $w->is_active
186 220
187Returns true if the watcher is active, false otherwise. 221Returns true if the watcher is active, false otherwise.
222
223=item $current_data = $w->data
224
225=item $old_data = $w->data ($new_data)
226
227Queries a freely usable data scalar on the watcher and optionally changes
228it. This is a way to associate custom data with a watcher:
229
230 my $w = EV::timer 60, 0, sub {
231 warn $_[0]->data;
232 };
233 $w->data ("print me!");
188 234
189=item $current_cb = $w->cb 235=item $current_cb = $w->cb
190 236
191=item $old_cb = $w->cb ($new_cb) 237=item $old_cb = $w->cb ($new_cb)
192 238
201watchers with higher priority will be invoked first. The valid range of 247watchers with higher priority will be invoked first. The valid range of
202priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default 248priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
203-2). If the priority is outside this range it will automatically be 249-2). If the priority is outside this range it will automatically be
204normalised to the nearest valid priority. 250normalised to the nearest valid priority.
205 251
206The default priority of any newly-created weatcher is 0. 252The default priority of any newly-created watcher is 0.
253
254Note that the priority semantics have not yet been fleshed out and are
255subject to almost certain change.
207 256
208=item $w->trigger ($revents) 257=item $w->trigger ($revents)
209 258
210Call the callback *now* with the given event mask. 259Call the callback *now* with the given event mask.
211 260
261=item $previous_state = $w->keepalive ($bool)
262
263Normally, C<EV::loop> will return when there are no active watchers
264(which is a "deadlock" because no progress can be made anymore). This is
265convinient because it allows you to start your watchers (and your jobs),
266call C<EV::loop> once and when it returns you know that all your jobs are
267finished (or they forgot to register some watchers for their task :).
268
269Sometimes, however, this gets in your way, for example when you the module
270that calls C<EV::loop> (usually the main program) is not the same module
271as a long-living watcher (for example a DNS client module written by
272somebody else even). Then you might want any outstanding requests to be
273handled, but you would not want to keep C<EV::loop> from returning just
274because you happen to have this long-running UDP port watcher.
275
276In this case you can clear the keepalive status, which means that even
277though your watcher is active, it won't keep C<EV::loop> from returning.
278
279The initial value for keepalive is true (enabled), and you cna change it
280any time.
281
282Example: Register an IO watcher for some UDP socket but do not keep the
283event loop from running just because of that watcher.
284
285 my $udp_socket = ...
286 my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... };
287 $udp_watcher->keepalive (0);
288
289=back
290
291
292=head2 WATCHER TYPES
293
294Each of the following subsections describes a single watcher type.
295
296=head3 IO WATCHERS - is this file descriptor readable or writable?
297
298=over 4
212 299
213=item $w = EV::io $fileno_or_fh, $eventmask, $callback 300=item $w = EV::io $fileno_or_fh, $eventmask, $callback
214 301
215=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 302=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
216 303
217As long as the returned watcher object is alive, call the C<$callback> 304As long as the returned watcher object is alive, call the C<$callback>
218when the events specified in C<$eventmask>. 305when at least one of events specified in C<$eventmask> occurs.
219 306
220The $eventmask can be one or more of these constants ORed together: 307The $eventmask can be one or more of these constants ORed together:
221 308
222 EV::READ wait until read() wouldn't block anymore 309 EV::READ wait until read() wouldn't block anymore
223 EV::WRITE wait until write() wouldn't block anymore 310 EV::WRITE wait until write() wouldn't block anymore
239 326
240=item $old_eventmask = $w->events ($new_eventmask) 327=item $old_eventmask = $w->events ($new_eventmask)
241 328
242Returns the previously set event mask and optionally set a new one. 329Returns the previously set event mask and optionally set a new one.
243 330
331=back
332
333
334=head3 TIMER WATCHERS - relative and optionally repeating timeouts
335
336=over 4
244 337
245=item $w = EV::timer $after, $repeat, $callback 338=item $w = EV::timer $after, $repeat, $callback
246 339
247=item $w = EV::timer_ns $after, $repeat, $callback 340=item $w = EV::timer_ns $after, $repeat, $callback
248 341
249Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 342Calls the callback after C<$after> seconds (which may be fractional). If
250the timer will be restarted (with the $repeat value as $after) after the 343C<$repeat> is non-zero, the timer will be restarted (with the $repeat
251callback returns. 344value as $after) after the callback returns.
252 345
253This means that the callback would be called roughly after C<$after> 346This means that the callback would be called roughly after C<$after>
254seconds, and then every C<$repeat> seconds. "Roughly" because the time of 347seconds, and then every C<$repeat> seconds. The timer does his best not
255callback processing is not taken into account, so the timer will slowly 348to drift, but it will not invoke the timer more often then once per event
256drift. If that isn't acceptable, look at EV::periodic. 349loop iteration, and might drift in other cases. If that isn't acceptable,
350look at EV::periodic, which can provide long-term stable timers.
257 351
258The timer is based on a monotonic clock, that is if somebody is sitting 352The timer is based on a monotonic clock, that is, if somebody is sitting
259in front of the machine while the timer is running and changes the system 353in front of the machine while the timer is running and changes the system
260clock, the timer will nevertheless run (roughly) the same time. 354clock, the timer will nevertheless run (roughly) the same time.
261 355
262The C<timer_ns> variant doesn't start (activate) the newly created watcher. 356The C<timer_ns> variant doesn't start (activate) the newly created watcher.
263 357
264=item $w->set ($after, $repeat) 358=item $w->set ($after, $repeat)
265 359
266Reconfigures the watcher, see the constructor above for details. Can be at 360Reconfigures the watcher, see the constructor above for details. Can be called at
267any time. 361any time.
268 362
269=item $w->again 363=item $w->again
270 364
271Similar to the C<start> method, but has special semantics for repeating timers: 365Similar to the C<start> method, but has special semantics for repeating timers:
366
367If the timer is active and non-repeating, it will be stopped.
272 368
273If the timer is active and repeating, reset the timeout to occur 369If the timer is active and repeating, reset the timeout to occur
274C<$repeat> seconds after now. 370C<$repeat> seconds after now.
275 371
276If the timer is active and non-repeating, it will be stopped.
277
278If the timer is in active and repeating, start it. 372If the timer is inactive and repeating, start it using the repeat value.
279 373
280Otherwise do nothing. 374Otherwise do nothing.
281 375
282This behaviour is useful when you have a timeout for some IO 376This behaviour is useful when you have a timeout for some IO
283operation. You create a timer object with the same value for C<$after> and 377operation. You create a timer object with the same value for C<$after> and
284C<$repeat>, and then, in the read/write watcher, run the C<again> method 378C<$repeat>, and then, in the read/write watcher, run the C<again> method
285on the timeout. 379on the timeout.
286 380
381=back
287 382
383
384=head3 PERIODIC WATCHERS - to cron or not to cron?
385
386=over 4
387
288=item $w = EV::periodic $at, $interval, $callback 388=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
289 389
290=item $w = EV::periodic_ns $at, $interval, $callback 390=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
291 391
292Similar to EV::timer, but the time is given as an absolute point in time 392Similar to EV::timer, but is not based on relative timeouts but on
293(C<$at>), plus an optional C<$interval>. 393absolute times. Apart from creating "simple" timers that trigger "at" the
394specified time, it can also be used for non-drifting absolute timers and
395more complex, cron-like, setups that are not adversely affected by time
396jumps (i.e. when the system clock is changed by explicit date -s or other
397means such as ntpd). It is also the most complex watcher type in EV.
294 398
295If the C<$interval> is zero, then the callback will be called at the time 399It has three distinct "modes":
296C<$at> if that is in the future, or as soon as possible if it is in the
297past. It will not automatically repeat.
298 400
299If the C<$interval> is nonzero, then the watcher will always be scheduled 401=over 4
300to time out at the next C<$at + N * $interval> time.
301 402
302This can be used to schedule a callback to run at very regular intervals, 403=item * absolute timer ($interval = $reschedule_cb = 0)
303as long as the processing time is less then the interval (otherwise 404
304obviously events will be skipped). 405This time simply fires at the wallclock time C<$at> and doesn't repeat. It
406will not adjust when a time jump occurs, that is, if it is to be run
407at January 1st 2011 then it will run when the system time reaches or
408surpasses this time.
409
410=item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0)
411
412In this mode the watcher will always be scheduled to time out at the
413next C<$at + N * $interval> time (for some integer N) and then repeat,
414regardless of any time jumps.
415
416This can be used to create timers that do not drift with respect to system
417time:
418
419 my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" };
420
421That doesn't mean there will always be 3600 seconds in between triggers,
422but only that the the clalback will be called when the system time shows a
423full hour (UTC).
305 424
306Another way to think about it (for the mathematically inclined) is that 425Another way to think about it (for the mathematically inclined) is that
307EV::periodic will try to run the callback at the next possible time where 426EV::periodic will try to run the callback in this mode at the next
308C<$time = $at (mod $interval)>, regardless of any time jumps. 427possible time where C<$time = $at (mod $interval)>, regardless of any time
428jumps.
309 429
310This periodic timer is based on "wallclock time", that is, if the clock 430=item * manual reschedule mode ($reschedule_cb = coderef)
311changes (C<ntp>, C<date -s> etc.), then the timer will nevertheless run at 431
312the specified time. This means it will never drift (it might jitter, but 432In this mode $interval and $at are both being ignored. Instead, each
313it will not drift). 433time the periodic watcher gets scheduled, the reschedule callback
434($reschedule_cb) will be called with the watcher as first, and the current
435time as second argument.
436
437I<This callback MUST NOT stop or destroy this or any other periodic
438watcher, ever>. If you need to stop it, return 1e30 and stop it
439afterwards.
440
441It must return the next time to trigger, based on the passed time value
442(that is, the lowest time value larger than to the second argument). It
443will usually be called just before the callback will be triggered, but
444might be called at other times, too.
445
446This can be used to create very complex timers, such as a timer that
447triggers on each midnight, local time (actually 24 hours after the last
448midnight, to keep the example simple. If you know a way to do it correctly
449in about the same space (without requiring elaborate modules), drop me a
450note :):
451
452 my $daily = EV::periodic 0, 0, sub {
453 my ($w, $now) = @_;
454
455 use Time::Local ();
456 my (undef, undef, undef, $d, $m, $y) = localtime $now;
457 86400 + Time::Local::timelocal 0, 0, 0, $d, $m, $y
458 }, sub {
459 print "it's midnight or likely shortly after, now\n";
460 };
461
462=back
314 463
315The C<periodic_ns> variant doesn't start (activate) the newly created watcher. 464The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
316 465
317=item $w->set ($at, $interval) 466=item $w->set ($at, $interval, $reschedule_cb)
318 467
319Reconfigures the watcher, see the constructor above for details. Can be at 468Reconfigures the watcher, see the constructor above for details. Can be called at
320any time. 469any time.
321 470
471=item $w->again
472
473Simply stops and starts the watcher again.
474
475=back
476
477
478=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
479
480=over 4
322 481
323=item $w = EV::signal $signal, $callback 482=item $w = EV::signal $signal, $callback
324 483
325=item $w = EV::signal_ns $signal, $callback 484=item $w = EV::signal_ns $signal, $callback
326 485
327Call the callback when $signal is received (the signal can be specified 486Call the callback when $signal is received (the signal can be specified by
328by number or by name, just as with kill or %SIG). 487number or by name, just as with C<kill> or C<%SIG>).
329 488
330EV will grab the signal for the process (the kernel only allows one 489EV will grab the signal for the process (the kernel only allows one
331component to receive a signal at a time) when you start a signal watcher, 490component to receive a signal at a time) when you start a signal watcher,
332and removes it again when you stop it. Perl does the same when you 491and removes it again when you stop it. Perl does the same when you
333add/remove callbacks to %SIG, so watch out. 492add/remove callbacks to C<%SIG>, so watch out.
334 493
335You can have as many signal watchers per signal as you want. 494You can have as many signal watchers per signal as you want.
336 495
337The C<signal_ns> variant doesn't start (activate) the newly created watcher. 496The C<signal_ns> variant doesn't start (activate) the newly created watcher.
338 497
339=item $w->set ($signal) 498=item $w->set ($signal)
340 499
341Reconfigures the watcher, see the constructor above for details. Can be at 500Reconfigures the watcher, see the constructor above for details. Can be
342any time. 501called at any time.
343 502
344=item $current_signum = $w->signal 503=item $current_signum = $w->signal
345 504
346=item $old_signum = $w->signal ($new_signal) 505=item $old_signum = $w->signal ($new_signal)
347 506
348Returns the previously set signal (always as a number not name) and 507Returns the previously set signal (always as a number not name) and
349optionally set a new one. 508optionally set a new one.
350 509
510=back
511
512
513=head3 CHILD WATCHERS - watch out for process status changes
514
515=over 4
351 516
352=item $w = EV::child $pid, $callback 517=item $w = EV::child $pid, $callback
353 518
354=item $w = EV::child_ns $pid, $callback 519=item $w = EV::child_ns $pid, $callback
355 520
356Call the callback when a status change for pid C<$pid> (or any pid 521Call the callback when a status change for pid C<$pid> (or any pid if
357if C<$pid> is 0) has been received. More precisely: when the process 522C<$pid> is 0) has been received. More precisely: when the process receives
358receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all 523a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
359changed/zombie children and call the callback. 524changed/zombie children and call the callback.
360 525
361Unlike all other callbacks, this callback will be called with an 526It is valid (and fully supported) to install a child watcher after a child
362additional third argument which is the exit status. See the C<waitpid> 527has exited but before the event loop has started its next iteration (for
363function for details. 528example, first you C<fork>, then the new child process might exit, and
529only then do you install a child watcher in the parent for the new pid).
364 530
531You can access both exit (or tracing) status and pid by using the
532C<rstatus> and C<rpid> methods on the watcher object.
533
365You can have as many pid watchers per pid as you want. 534You can have as many pid watchers per pid as you want, they will all be
535called.
366 536
367The C<child_ns> variant doesn't start (activate) the newly created watcher. 537The C<child_ns> variant doesn't start (activate) the newly created watcher.
368 538
369=item $w->set ($pid) 539=item $w->set ($pid)
370 540
371Reconfigures the watcher, see the constructor above for details. Can be at 541Reconfigures the watcher, see the constructor above for details. Can be called at
372any time. 542any time.
373 543
374=item $current_pid = $w->pid 544=item $current_pid = $w->pid
375 545
376=item $old_pid = $w->pid ($new_pid) 546=item $old_pid = $w->pid ($new_pid)
377 547
378Returns the previously set process id and optionally set a new one. 548Returns the previously set process id and optionally set a new one.
379 549
550=item $exit_status = $w->rstatus
551
552Return the exit/wait status (as returned by waitpid, see the waitpid entry
553in perlfunc).
554
555=item $pid = $w->rpid
556
557Return the pid of the awaited child (useful when you have installed a
558watcher for all pids).
559
560=back
561
562
563=head3 STAT WATCHERS - did the file attributes just change?
564
565=over 4
566
567=item $w = EV::stat $path, $interval, $callback
568
569=item $w = EV::stat_ns $path, $interval, $callback
570
571Call the callback when a file status change has been detected on
572C<$path>. The C<$path> does not need to exist, changing from "path exists"
573to "path does not exist" is a status change like any other.
574
575The C<$interval> is a recommended polling interval for systems where
576OS-supported change notifications don't exist or are not supported. If
577you use C<0> then an unspecified default is used (which is highly
578recommended!), which is to be expected to be around five seconds usually.
579
580This watcher type is not meant for massive numbers of stat watchers,
581as even with OS-supported change notifications, this can be
582resource-intensive.
583
584The C<stat_ns> variant doesn't start (activate) the newly created watcher.
585
586=item ... = $w->stat
587
588This call is very similar to the perl C<stat> built-in: It stats (using
589C<lstat>) the path specified in the watcher and sets perls stat cache (as
590well as EV's idea of the current stat values) to the values found.
591
592In scalar context, a boolean is return indicating success or failure of
593the stat. In list context, the same 13-value list as with stat is returned
594(except that the blksize and blocks fields are not reliable).
595
596In the case of an error, errno is set to C<ENOENT> (regardless of the
597actual error value) and the C<nlink> value is forced to zero (if the stat
598was successful then nlink is guaranteed to be non-zero).
599
600See also the next two entries for more info.
601
602=item ... = $w->attr
603
604Just like C<< $w->stat >>, but without the initial stat'ing: this returns
605the values most recently detected by EV. See the next entry for more info.
606
607=item ... = $w->prev
608
609Just like C<< $w->stat >>, but without the initial stat'ing: this returns
610the previous set of values, before the change.
611
612That is, when the watcher callback is invoked, C<< $w->prev >> will be set
613to the values found I<before> a change was detected, while C<< $w->attr >>
614returns the values found leading to the change detection. The difference (if any)
615between C<prev> and C<attr> is what triggered the callback.
616
617If you did something to the filesystem object and do not want to trigger
618yet another change, you can call C<stat> to update EV's idea of what the
619current attributes are.
620
621=item $w->set ($path, $interval)
622
623Reconfigures the watcher, see the constructor above for details. Can be
624called at any time.
625
626=item $current_path = $w->path
627
628=item $old_path = $w->path ($new_path)
629
630Returns the previously set path and optionally set a new one.
631
632=item $current_interval = $w->interval
633
634=item $old_interval = $w->interval ($new_interval)
635
636Returns the previously set interval and optionally set a new one. Can be
637used to query the actual interval used.
638
639=back
640
641
642=head3 IDLE WATCHERS - when you've got nothing better to do...
643
644=over 4
380 645
381=item $w = EV::idle $callback 646=item $w = EV::idle $callback
382 647
383=item $w = EV::idle_ns $callback 648=item $w = EV::idle_ns $callback
384 649
388The process will not block as long as any idle watchers are active, and 653The process will not block as long as any idle watchers are active, and
389they will be called repeatedly until stopped. 654they will be called repeatedly until stopped.
390 655
391The C<idle_ns> variant doesn't start (activate) the newly created watcher. 656The C<idle_ns> variant doesn't start (activate) the newly created watcher.
392 657
658=back
659
660
661=head3 PREPARE WATCHERS - customise your event loop!
662
663=over 4
393 664
394=item $w = EV::prepare $callback 665=item $w = EV::prepare $callback
395 666
396=item $w = EV::prepare_ns $callback 667=item $w = EV::prepare_ns $callback
397 668
400 671
401See the EV::check watcher, below, for explanations and an example. 672See the EV::check watcher, below, for explanations and an example.
402 673
403The C<prepare_ns> variant doesn't start (activate) the newly created watcher. 674The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
404 675
676=back
677
678
679=head3 CHECK WATCHERS - customise your event loop even more!
680
681=over 4
405 682
406=item $w = EV::check $callback 683=item $w = EV::check $callback
407 684
408=item $w = EV::check_ns $callback 685=item $w = EV::check_ns $callback
409 686
421 # do nothing unless active 698 # do nothing unless active
422 $dispatcher->{_event_queue_h} 699 $dispatcher->{_event_queue_h}
423 or return; 700 or return;
424 701
425 # make the dispatcher handle any outstanding stuff 702 # make the dispatcher handle any outstanding stuff
703 ... not shown
426 704
427 # create an IO watcher for each and every socket 705 # create an IO watcher for each and every socket
428 @snmp_watcher = ( 706 @snmp_watcher = (
429 (map { EV::io $_, EV::READ, sub { } } 707 (map { EV::io $_, EV::READ, sub { } }
430 keys %{ $dispatcher->{_descriptors} }), 708 keys %{ $dispatcher->{_descriptors} }),
709
710 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
711 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
712 0, sub { },
431 ); 713 );
432
433 # if there are any timeouts, also create a timer
434 push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { }
435 if $event->[Net::SNMP::Dispatcher::_ACTIVE];
436 }; 714 };
437 715
438The callbacks are irrelevant, the only purpose of those watchers is 716The callbacks are irrelevant (and are not even being called), the
439to wake up the process as soon as one of those events occurs (socket 717only purpose of those watchers is to wake up the process as soon as
440readable, or timer timed out). The corresponding EV::check watcher will then 718one of those events occurs (socket readable, or timer timed out). The
441clean up: 719corresponding EV::check watcher will then clean up:
442 720
443 our $snmp_check = EV::check sub { 721 our $snmp_check = EV::check sub {
444 # destroy all watchers 722 # destroy all watchers
445 @snmp_watcher = (); 723 @snmp_watcher = ();
446 724
447 # make the dispatcher handle any new stuff 725 # make the dispatcher handle any new stuff
726 ... not shown
448 }; 727 };
449 728
450The callbacks of the created watchers will not be called as the watchers 729The callbacks of the created watchers will not be called as the watchers
451are destroyed before this cna happen (remember EV::check gets called 730are destroyed before this cna happen (remember EV::check gets called
452first). 731first).
453 732
454The C<check_ns> variant doesn't start (activate) the newly created watcher. 733The C<check_ns> variant doesn't start (activate) the newly created watcher.
455 734
456=back 735=back
457 736
737
738=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
739
740Fork watchers are called when a C<fork ()> was detected. The invocation
741is done before the event loop blocks next and before C<check> watchers
742are being called, and only in the child after the fork.
743
744=over 4
745
746=item $w = EV::fork $callback
747
748=item $w = EV::fork_ns $callback
749
750Call the callback before the event loop is resumed in the child process
751after a fork.
752
753The C<fork_ns> variant doesn't start (activate) the newly created watcher.
754
755=back
756
757
758=head1 PERL SIGNALS
759
760While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
761with EV is as the same as any other C library: Perl-signals will only be
762handled when Perl runs, which means your signal handler might be invoked
763only the next time an event callback is invoked.
764
765The solution is to use EV signal watchers (see C<EV::signal>), which will
766ensure proper operations with regards to other event watchers.
767
768If you cannot do this for whatever reason, you can also force a watcher
769to be called on every event loop iteration by installing a C<EV::check>
770watcher:
771
772 my $async_check = EV::check sub { };
773
774This ensures that perl shortly gets into control for a short time, and
775also ensures slower overall operation.
776
458=head1 THREADS 777=head1 THREADS
459 778
460Threads are not supported by this in any way. Perl pseudo-threads is evil 779Threads are not supported by this module in any way. Perl pseudo-threads
461stuff and must die. 780is evil stuff and must die. As soon as Perl gains real threads I will work
781on thread support for it.
782
783=head1 FORK
784
785Most of the "improved" event delivering mechanisms of modern operating
786systems have quite a few problems with fork(2) (to put it bluntly: it is
787not supported and usually destructive). Libev makes it possible to work
788around this by having a function that recreates the kernel state after
789fork in the child.
790
791On non-win32 platforms, this module requires the pthread_atfork
792functionality to do this automatically for you. This function is quite
793buggy on most BSDs, though, so YMMV. The overhead for this is quite
794negligible, because everything the function currently does is set a flag
795that is checked only when the event loop gets used the next time, so when
796you do fork but not use EV, the overhead is minimal.
797
798On win32, there is no notion of fork so all this doesn't apply, of course.
462 799
463=cut 800=cut
464 801
465our $DIED = sub { 802our $DIED = sub {
466 warn "EV: error in callback (ignoring): $@"; 803 warn "EV: error in callback (ignoring): $@";
467}; 804};
468 805
469init; 806default_loop
470 807 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?';
471push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
472 808
4731; 8091;
474 810
475=head1 SEE ALSO 811=head1 SEE ALSO
476 812
477 L<EV::DNS>, L<EV::AnyEvent>. 813L<EV::ADNS> (asynchronous dns), L<Glib::EV> (makes Glib/Gtk2 use EV as
814event loop), L<Coro::EV> (efficient coroutines with EV).
478 815
479=head1 AUTHOR 816=head1 AUTHOR
480 817
481 Marc Lehmann <schmorp@schmorp.de> 818 Marc Lehmann <schmorp@schmorp.de>
482 http://home.schmorp.de/ 819 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines