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

Comparing EV/EV.pm (file contents):
Revision 1.25 by root, Fri Nov 2 22:18:49 2007 UTC vs.
Revision 1.58 by root, Wed Nov 28 19:22:16 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.5'; 72 our $VERSION = '1.5';
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 EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
126 137
138This function rolls together an I/O and a timer watcher for a single
139one-shot event without the need for managing a watcher object.
140
141If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
142must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
143| EV::WRITE>, indicating the type of I/O event you want to wait for. If
144you do not want to wait for some I/O event, specify C<undef> for
145C<$fh_or_undef> and C<0> for C<$events>).
146
147If timeout is C<undef> or negative, then there will be no
148timeout. Otherwise a EV::timer with this value will be started.
149
150When an error occurs or either the timeout or I/O watcher triggers, then
151the callback will be called with the received event set (in general
152you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>,
153C<EV::WRITE> and C<EV::TIMEOUT>).
154
155EV::once doesn't return anything: the watchers stay active till either
156of them triggers, then they will be stopped and freed, and the callback
157invoked.
158
159=back
160
127=head2 WATCHER 161=head2 WATCHER OBJECTS
128 162
129A watcher is an object that gets created to record your interest in some 163A 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 164event. For instance, if you want to wait for STDIN to become readable, you
131would create an EV::io watcher for that: 165would create an EV::io watcher for that:
132 166
157 191
158Also, all methods changing some aspect of a watcher (->set, ->priority, 192Also, 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, 193->fh and so on) automatically stop and start it again if it is active,
160which means pending events get lost. 194which means pending events get lost.
161 195
162=head2 WATCHER TYPES 196=head2 COMMON WATCHER METHODS
163 197
164Now lets move to the existing watcher types and asociated methods. 198This 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 199
171=over 4 200=over 4
172 201
173=item $w->start 202=item $w->start
174 203
183regardless of wether the watcher was active or not. 212regardless of wether the watcher was active or not.
184 213
185=item $bool = $w->is_active 214=item $bool = $w->is_active
186 215
187Returns true if the watcher is active, false otherwise. 216Returns true if the watcher is active, false otherwise.
217
218=item $current_data = $w->data
219
220=item $old_data = $w->data ($new_data)
221
222Queries a freely usable data scalar on the watcher and optionally changes
223it. This is a way to associate custom data with a watcher:
224
225 my $w = EV::timer 60, 0, sub {
226 warn $_[0]->data;
227 };
228 $w->data ("print me!");
188 229
189=item $current_cb = $w->cb 230=item $current_cb = $w->cb
190 231
191=item $old_cb = $w->cb ($new_cb) 232=item $old_cb = $w->cb ($new_cb)
192 233
201watchers with higher priority will be invoked first. The valid range of 242watchers with higher priority will be invoked first. The valid range of
202priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default 243priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
203-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
204normalised to the nearest valid priority. 245normalised to the nearest valid priority.
205 246
206The default priority of any newly-created weatcher is 0. 247The default priority of any newly-created watcher is 0.
248
249Note that the priority semantics have not yet been fleshed out and are
250subject to almost certain change.
207 251
208=item $w->trigger ($revents) 252=item $w->trigger ($revents)
209 253
210Call the callback *now* with the given event mask. 254Call the callback *now* with the given event mask.
211 255
256=item $previous_state = $w->keepalive ($bool)
257
258Normally, 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
260convinient because it allows you to start your watchers (and your jobs),
261call C<EV::loop> once and when it returns you know that all your jobs are
262finished (or they forgot to register some watchers for their task :).
263
264Sometimes, however, this gets in your way, for example when you the module
265that calls C<EV::loop> (usually the main program) is not the same module
266as a long-living watcher (for example a DNS client module written by
267somebody else even). Then you might want any outstanding requests to be
268handled, but you would not want to keep C<EV::loop> from returning just
269because you happen to have this long-running UDP port watcher.
270
271In this case you can clear the keepalive status, which means that even
272though your watcher is active, it won't keep C<EV::loop> from returning.
273
274The initial value for keepalive is true (enabled), and you cna change it
275any time.
276
277Example: Register an IO watcher for some UDP socket but do not keep the
278event 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
289Each 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
212 294
213=item $w = EV::io $fileno_or_fh, $eventmask, $callback 295=item $w = EV::io $fileno_or_fh, $eventmask, $callback
214 296
215=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 297=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
216 298
217As long as the returned watcher object is alive, call the C<$callback> 299As long as the returned watcher object is alive, call the C<$callback>
218when the events specified in C<$eventmask>. 300when at least one of events specified in C<$eventmask> occurs.
219 301
220The $eventmask can be one or more of these constants ORed together: 302The $eventmask can be one or more of these constants ORed together:
221 303
222 EV::READ wait until read() wouldn't block anymore 304 EV::READ wait until read() wouldn't block anymore
223 EV::WRITE wait until write() wouldn't block anymore 305 EV::WRITE wait until write() wouldn't block anymore
239 321
240=item $old_eventmask = $w->events ($new_eventmask) 322=item $old_eventmask = $w->events ($new_eventmask)
241 323
242Returns the previously set event mask and optionally set a new one. 324Returns the previously set event mask and optionally set a new one.
243 325
326=back
327
328
329=head3 TIMER WATCHERS - relative and optionally repeating timeouts
330
331=over 4
244 332
245=item $w = EV::timer $after, $repeat, $callback 333=item $w = EV::timer $after, $repeat, $callback
246 334
247=item $w = EV::timer_ns $after, $repeat, $callback 335=item $w = EV::timer_ns $after, $repeat, $callback
248 336
249Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 337Calls the callback after C<$after> seconds (which may be fractional). If
250the timer will be restarted (with the $repeat value as $after) after the 338C<$repeat> is non-zero, the timer will be restarted (with the $repeat
251callback returns. 339value as $after) after the callback returns.
252 340
253This means that the callback would be called roughly after C<$after> 341This means that the callback would be called roughly after C<$after>
254seconds, and then every C<$repeat> seconds. "Roughly" because the time of 342seconds, and then every C<$repeat> seconds. The timer does his best not
255callback processing is not taken into account, so the timer will slowly 343to drift, but it will not invoke the timer more often then once per event
256drift. If that isn't acceptable, look at EV::periodic. 344loop iteration, and might drift in other cases. If that isn't acceptable,
345look at EV::periodic, which can provide long-term stable timers.
257 346
258The timer is based on a monotonic clock, that is if somebody is sitting 347The 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 348in front of the machine while the timer is running and changes the system
260clock, the timer will nevertheless run (roughly) the same time. 349clock, the timer will nevertheless run (roughly) the same time.
261 350
262The C<timer_ns> variant doesn't start (activate) the newly created watcher. 351The C<timer_ns> variant doesn't start (activate) the newly created watcher.
263 352
264=item $w->set ($after, $repeat) 353=item $w->set ($after, $repeat)
265 354
266Reconfigures the watcher, see the constructor above for details. Can be at 355Reconfigures the watcher, see the constructor above for details. Can be called at
267any time. 356any time.
268 357
269=item $w->again 358=item $w->again
270 359
271Similar to the C<start> method, but has special semantics for repeating timers: 360Similar to the C<start> method, but has special semantics for repeating timers:
361
362If the timer is active and non-repeating, it will be stopped.
272 363
273If the timer is active and repeating, reset the timeout to occur 364If the timer is active and repeating, reset the timeout to occur
274C<$repeat> seconds after now. 365C<$repeat> seconds after now.
275 366
276If the timer is active and non-repeating, it will be stopped.
277
278If the timer is in active and repeating, start it. 367If the timer is inactive and repeating, start it using the repeat value.
279 368
280Otherwise do nothing. 369Otherwise do nothing.
281 370
282This behaviour is useful when you have a timeout for some IO 371This 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 372operation. 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 373C<$repeat>, and then, in the read/write watcher, run the C<again> method
285on the timeout. 374on the timeout.
286 375
376=back
287 377
378
379=head3 PERIODIC WATCHERS - to cron or not to cron?
380
381=over 4
382
288=item $w = EV::periodic $at, $interval, $callback 383=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
289 384
290=item $w = EV::periodic_ns $at, $interval, $callback 385=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
291 386
292Similar to EV::timer, but the time is given as an absolute point in time 387Similar to EV::timer, but is not based on relative timeouts but on
293(C<$at>), plus an optional C<$interval>. 388absolute times. Apart from creating "simple" timers that trigger "at" the
389specified time, it can also be used for non-drifting absolute timers and
390more complex, cron-like, setups that are not adversely affected by time
391jumps (i.e. when the system clock is changed by explicit date -s or other
392means such as ntpd). It is also the most complex watcher type in EV.
294 393
295If the C<$interval> is zero, then the callback will be called at the time 394It 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 395
299If the C<$interval> is nonzero, then the watcher will always be scheduled 396=over 4
300to time out at the next C<$at + N * $interval> time.
301 397
302This can be used to schedule a callback to run at very regular intervals, 398=item * absolute timer ($interval = $reschedule_cb = 0)
303as long as the processing time is less then the interval (otherwise 399
304obviously events will be skipped). 400This time simply fires at the wallclock time C<$at> and doesn't repeat. It
401will not adjust when a time jump occurs, that is, if it is to be run
402at January 1st 2011 then it will run when the system time reaches or
403surpasses this time.
404
405=item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0)
406
407In this mode the watcher will always be scheduled to time out at the
408next C<$at + N * $interval> time (for some integer N) and then repeat,
409regardless of any time jumps.
410
411This can be used to create timers that do not drift with respect to system
412time:
413
414 my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" };
415
416That doesn't mean there will always be 3600 seconds in between triggers,
417but only that the the clalback will be called when the system time shows a
418full hour (UTC).
305 419
306Another way to think about it (for the mathematically inclined) is that 420Another 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 421EV::periodic will try to run the callback in this mode at the next
308C<$time = $at (mod $interval)>, regardless of any time jumps. 422possible time where C<$time = $at (mod $interval)>, regardless of any time
423jumps.
309 424
310This periodic timer is based on "wallclock time", that is, if the clock 425=item * manual reschedule mode ($reschedule_cb = coderef)
311changes (C<ntp>, C<date -s> etc.), then the timer will nevertheless run at 426
312the specified time. This means it will never drift (it might jitter, but 427In this mode $interval and $at are both being ignored. Instead, each
313it will not drift). 428time the periodic watcher gets scheduled, the reschedule callback
429($reschedule_cb) will be called with the watcher as first, and the current
430time as second argument.
431
432I<This callback MUST NOT stop or destroy this or any other periodic
433watcher, ever>. If you need to stop it, return 1e30 and stop it
434afterwards.
435
436It must return the next time to trigger, based on the passed time value
437(that is, the lowest time value larger than to the second argument). It
438will usually be called just before the callback will be triggered, but
439might be called at other times, too.
440
441This can be used to create very complex timers, such as a timer that
442triggers on each midnight, local time (actually 24 hours after the last
443midnight, to keep the example simple. If you know a way to do it correctly
444in about the same space (without requiring elaborate modules), drop me a
445note :):
446
447 my $daily = EV::periodic 0, 0, sub {
448 my ($w, $now) = @_;
449
450 use Time::Local ();
451 my (undef, undef, undef, $d, $m, $y) = localtime $now;
452 86400 + Time::Local::timelocal 0, 0, 0, $d, $m, $y
453 }, sub {
454 print "it's midnight or likely shortly after, now\n";
455 };
456
457=back
314 458
315The C<periodic_ns> variant doesn't start (activate) the newly created watcher. 459The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
316 460
317=item $w->set ($at, $interval) 461=item $w->set ($at, $interval, $reschedule_cb)
318 462
319Reconfigures the watcher, see the constructor above for details. Can be at 463Reconfigures the watcher, see the constructor above for details. Can be called at
320any time. 464any time.
321 465
466=item $w->again
467
468Simply stops and starts the watcher again.
469
470=back
471
472
473=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
474
475=over 4
322 476
323=item $w = EV::signal $signal, $callback 477=item $w = EV::signal $signal, $callback
324 478
325=item $w = EV::signal_ns $signal, $callback 479=item $w = EV::signal_ns $signal, $callback
326 480
327Call the callback when $signal is received (the signal can be specified 481Call the callback when $signal is received (the signal can be specified by
328by number or by name, just as with kill or %SIG). 482number or by name, just as with C<kill> or C<%SIG>).
329 483
330EV will grab the signal for the process (the kernel only allows one 484EV 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, 485component 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 486and removes it again when you stop it. Perl does the same when you
333add/remove callbacks to %SIG, so watch out. 487add/remove callbacks to C<%SIG>, so watch out.
334 488
335You can have as many signal watchers per signal as you want. 489You can have as many signal watchers per signal as you want.
336 490
337The C<signal_ns> variant doesn't start (activate) the newly created watcher. 491The C<signal_ns> variant doesn't start (activate) the newly created watcher.
338 492
339=item $w->set ($signal) 493=item $w->set ($signal)
340 494
341Reconfigures the watcher, see the constructor above for details. Can be at 495Reconfigures the watcher, see the constructor above for details. Can be
342any time. 496called at any time.
343 497
344=item $current_signum = $w->signal 498=item $current_signum = $w->signal
345 499
346=item $old_signum = $w->signal ($new_signal) 500=item $old_signum = $w->signal ($new_signal)
347 501
348Returns the previously set signal (always as a number not name) and 502Returns the previously set signal (always as a number not name) and
349optionally set a new one. 503optionally set a new one.
350 504
505=back
506
507
508=head3 CHILD WATCHERS - watch out for process status changes
509
510=over 4
351 511
352=item $w = EV::child $pid, $callback 512=item $w = EV::child $pid, $callback
353 513
354=item $w = EV::child_ns $pid, $callback 514=item $w = EV::child_ns $pid, $callback
355 515
356Call the callback when a status change for pid C<$pid> (or any pid 516Call 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 517C<$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 518a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
359changed/zombie children and call the callback. 519changed/zombie children and call the callback.
360 520
361Unlike all other callbacks, this callback will be called with an 521It 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> 522has exited but before the event loop has started its next iteration (for
363function for details. 523example, first you C<fork>, then the new child process might exit, and
524only then do you install a child watcher in the parent for the new pid).
364 525
526You can access both exit (or tracing) status and pid by using the
527C<rstatus> and C<rpid> methods on the watcher object.
528
365You can have as many pid watchers per pid as you want. 529You can have as many pid watchers per pid as you want, they will all be
530called.
366 531
367The C<child_ns> variant doesn't start (activate) the newly created watcher. 532The C<child_ns> variant doesn't start (activate) the newly created watcher.
368 533
369=item $w->set ($pid) 534=item $w->set ($pid)
370 535
371Reconfigures the watcher, see the constructor above for details. Can be at 536Reconfigures the watcher, see the constructor above for details. Can be called at
372any time. 537any time.
373 538
374=item $current_pid = $w->pid 539=item $current_pid = $w->pid
375 540
376=item $old_pid = $w->pid ($new_pid) 541=item $old_pid = $w->pid ($new_pid)
377 542
378Returns the previously set process id and optionally set a new one. 543Returns the previously set process id and optionally set a new one.
379 544
545=item $exit_status = $w->rstatus
546
547Return the exit/wait status (as returned by waitpid, see the waitpid entry
548in perlfunc).
549
550=item $pid = $w->rpid
551
552Return the pid of the awaited child (useful when you have installed a
553watcher for all pids).
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
566Call the callback when a file status change has been detected on
567C<$path>. The C<$path> does not need to exist, changing from "path exists"
568to "path does not exist" is a status change like any other.
569
570The C<$interval> is a recommended polling interval for systems where
571OS-supported change notifications don't exist or are not supported. If
572you use C<0> then an unspecified default is used (which is highly
573recommended!), which is to be expected to be around five seconds usually.
574
575This watcher type is not meant for massive numbers of stat watchers,
576as even with OS-supported change notifications, this can be
577resource-intensive.
578
579The C<stat_ns> variant doesn't start (activate) the newly created watcher.
580
581=item ... = $w->stat
582
583This call is very similar to the perl C<stat> built-in: It stats (using
584C<lstat>) the path specified in the watcher and sets perls stat cache (as
585well as EV's idea of the current stat values) to the values found.
586
587In scalar context, a boolean is return indicating success or failure of
588the 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
591In the case of an error, errno is set to C<ENOENT> (regardless of the
592actual error value) and the C<nlink> value is forced to zero (if the stat
593was successful then nlink is guaranteed to be non-zero).
594
595See also the next two entries for more info.
596
597=item ... = $w->attr
598
599Just like C<< $w->stat >>, but without the initial stat'ing: this returns
600the values most recently detected by EV. See the next entry for more info.
601
602=item ... = $w->prev
603
604Just like C<< $w->stat >>, but without the initial stat'ing: this returns
605the previous set of values, before the change.
606
607That is, when the watcher callback is invoked, C<< $w->prev >> will be set
608to the values found I<before> a change was detected, while C<< $w->attr >>
609returns the values found leading to the change detection. The difference (if any)
610between C<prev> and C<attr> is what triggered the callback.
611
612If you did something to the filesystem object and do not want to trigger
613yet another change, you can call C<stat> to update EV's idea of what the
614current attributes are.
615
616=item $w->set ($path, $interval)
617
618Reconfigures the watcher, see the constructor above for details. Can be
619called at any time.
620
621=item $current_path = $w->path
622
623=item $old_path = $w->path ($new_path)
624
625Returns 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
631Returns the previously set interval and optionally set a new one. Can be
632used 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
380 640
381=item $w = EV::idle $callback 641=item $w = EV::idle $callback
382 642
383=item $w = EV::idle_ns $callback 643=item $w = EV::idle_ns $callback
384 644
388The process will not block as long as any idle watchers are active, and 648The process will not block as long as any idle watchers are active, and
389they will be called repeatedly until stopped. 649they will be called repeatedly until stopped.
390 650
391The C<idle_ns> variant doesn't start (activate) the newly created watcher. 651The C<idle_ns> variant doesn't start (activate) the newly created watcher.
392 652
653=back
654
655
656=head3 PREPARE WATCHERS - customise your event loop!
657
658=over 4
393 659
394=item $w = EV::prepare $callback 660=item $w = EV::prepare $callback
395 661
396=item $w = EV::prepare_ns $callback 662=item $w = EV::prepare_ns $callback
397 663
400 666
401See the EV::check watcher, below, for explanations and an example. 667See the EV::check watcher, below, for explanations and an example.
402 668
403The C<prepare_ns> variant doesn't start (activate) the newly created watcher. 669The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
404 670
671=back
672
673
674=head3 CHECK WATCHERS - customise your event loop even more!
675
676=over 4
405 677
406=item $w = EV::check $callback 678=item $w = EV::check $callback
407 679
408=item $w = EV::check_ns $callback 680=item $w = EV::check_ns $callback
409 681
421 # do nothing unless active 693 # do nothing unless active
422 $dispatcher->{_event_queue_h} 694 $dispatcher->{_event_queue_h}
423 or return; 695 or return;
424 696
425 # make the dispatcher handle any outstanding stuff 697 # make the dispatcher handle any outstanding stuff
698 ... not shown
426 699
427 # create an IO watcher for each and every socket 700 # create an IO watcher for each and every socket
428 @snmp_watcher = ( 701 @snmp_watcher = (
429 (map { EV::io $_, EV::READ, sub { } } 702 (map { EV::io $_, EV::READ, sub { } }
430 keys %{ $dispatcher->{_descriptors} }), 703 keys %{ $dispatcher->{_descriptors} }),
704
705 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
706 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
707 0, sub { },
431 ); 708 );
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 }; 709 };
437 710
438The callbacks are irrelevant, the only purpose of those watchers is 711The callbacks are irrelevant (and are not even being called), the
439to wake up the process as soon as one of those events occurs (socket 712only 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 713one of those events occurs (socket readable, or timer timed out). The
441clean up: 714corresponding EV::check watcher will then clean up:
442 715
443 our $snmp_check = EV::check sub { 716 our $snmp_check = EV::check sub {
444 # destroy all watchers 717 # destroy all watchers
445 @snmp_watcher = (); 718 @snmp_watcher = ();
446 719
447 # make the dispatcher handle any new stuff 720 # make the dispatcher handle any new stuff
721 ... not shown
448 }; 722 };
449 723
450The callbacks of the created watchers will not be called as the watchers 724The callbacks of the created watchers will not be called as the watchers
451are destroyed before this cna happen (remember EV::check gets called 725are destroyed before this cna happen (remember EV::check gets called
452first). 726first).
453 727
454The C<check_ns> variant doesn't start (activate) the newly created watcher. 728The C<check_ns> variant doesn't start (activate) the newly created watcher.
455 729
456=back 730=back
457 731
732
733=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
734
735Fork watchers are called when a C<fork ()> was detected. The invocation
736is done before the event loop blocks next and before C<check> watchers
737are 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
745Call the callback before the event loop is resumed in the child process
746after a fork.
747
748The C<fork_ns> variant doesn't start (activate) the newly created watcher.
749
750=back
751
752
458=head1 THREADS 753=head1 THREADS
459 754
460Threads are not supported by this in any way. Perl pseudo-threads is evil 755Threads are not supported by this module in any way. Perl pseudo-threads
461stuff and must die. 756is evil stuff and must die. As soon as Perl gains real threads I will work
757on thread support for it.
758
759=head1 FORK
760
761Most of the "improved" event delivering mechanisms of modern operating
762systems have quite a few problems with fork(2) (to put it bluntly: it is
763not supported and usually destructive). Libev makes it possible to work
764around this by having a function that recreates the kernel state after
765fork in the child.
766
767On non-win32 platforms, this module requires the pthread_atfork
768functionality to do this automatically for you. This function is quite
769buggy on most BSDs, though, so YMMV. The overhead for this is quite
770negligible, because everything the function currently does is set a flag
771that is checked only when the event loop gets used the next time, so when
772you do fork but not use EV, the overhead is minimal.
773
774On win32, there is no notion of fork so all this doesn't apply, of course.
462 775
463=cut 776=cut
464 777
465our $DIED = sub { 778our $DIED = sub {
466 warn "EV: error in callback (ignoring): $@"; 779 warn "EV: error in callback (ignoring): $@";
467}; 780};
468 781
469init; 782default_loop
470 783 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?';
471push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
472 784
4731; 7851;
474 786
475=head1 SEE ALSO 787=head1 SEE ALSO
476 788
477 L<EV::DNS>, L<EV::AnyEvent>. 789L<EV::DNS>.
478 790
479=head1 AUTHOR 791=head1 AUTHOR
480 792
481 Marc Lehmann <schmorp@schmorp.de> 793 Marc Lehmann <schmorp@schmorp.de>
482 http://home.schmorp.de/ 794 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines