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

Comparing EV/EV.pm (file contents):
Revision 1.21 by root, Thu Nov 1 17:20:25 2007 UTC vs.
Revision 1.56 by root, Tue Nov 27 10:59:10 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.4';
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
150In the rare case where one wants to create a watcher but not start it at 184In the rare case where one wants to create a watcher but not start it at
151the same time, each constructor has a variant with a trailing C<_ns> in 185the same time, each constructor has a variant with a trailing C<_ns> in
152its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. 186its name, e.g. EV::io has a non-starting variant EV::io_ns and so on.
153 187
154Please note that a watcher will automatically be stopped when the watcher 188Please note that a watcher will automatically be stopped when the watcher
155object is returned, so you I<need> to keep the watcher objects returned by 189object is destroyed, so you I<need> to keep the watcher objects returned by
156the constructors. 190the constructors.
157 191
158=head2 WATCHER TYPES 192Also, all methods changing some aspect of a watcher (->set, ->priority,
193->fh and so on) automatically stop and start it again if it is active,
194which means pending events get lost.
159 195
160Now lets move to the existing watcher types and asociated methods. 196=head2 COMMON WATCHER METHODS
161 197
162The following methods are available for all watchers. Then followes a 198This section lists methods common to all watchers.
163description of each watcher constructor (EV::io, EV::timer, EV::periodic,
164EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by
165any type-specific methods (if any).
166 199
167=over 4 200=over 4
168 201
169=item $w->start 202=item $w->start
170 203
180 213
181=item $bool = $w->is_active 214=item $bool = $w->is_active
182 215
183Returns true if the watcher is active, false otherwise. 216Returns true if the watcher is active, false otherwise.
184 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!");
229
185=item $current_cb = $w->cb 230=item $current_cb = $w->cb
186 231
187=item $old_cb = $w->cb ($new_cb) 232=item $old_cb = $w->cb ($new_cb)
188 233
189Queries the callback on the watcher and optionally changes it. You cna do 234Queries the callback on the watcher and optionally changes it. You can do
190this at any time. 235this at any time without the watcher restarting.
236
237=item $current_priority = $w->priority
238
239=item $old_priority = $w->priority ($new_priority)
240
241Queries the priority on the watcher and optionally changes it. Pending
242watchers with higher priority will be invoked first. The valid range of
243priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
244-2). If the priority is outside this range it will automatically be
245normalised to the nearest valid priority.
246
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.
191 251
192=item $w->trigger ($revents) 252=item $w->trigger ($revents)
193 253
194Call the callback *now* with the given event mask. 254Call the callback *now* with the given event mask.
195 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
196 294
197=item $w = EV::io $fileno_or_fh, $eventmask, $callback 295=item $w = EV::io $fileno_or_fh, $eventmask, $callback
198 296
199=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 297=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
200 298
201As 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>
202when the events specified in C<$eventmask>. 300when at least one of events specified in C<$eventmask> occurs.
203 301
204The $eventmask can be one or more of these constants ORed together: 302The $eventmask can be one or more of these constants ORed together:
205 303
206 EV::READ wait until read() wouldn't block anymore 304 EV::READ wait until read() wouldn't block anymore
207 EV::WRITE wait until write() wouldn't block anymore 305 EV::WRITE wait until write() wouldn't block anymore
223 321
224=item $old_eventmask = $w->events ($new_eventmask) 322=item $old_eventmask = $w->events ($new_eventmask)
225 323
226Returns the previously set event mask and optionally set a new one. 324Returns the previously set event mask and optionally set a new one.
227 325
326=back
327
328
329=head3 TIMER WATCHERS - relative and optionally repeating timeouts
330
331=over 4
228 332
229=item $w = EV::timer $after, $repeat, $callback 333=item $w = EV::timer $after, $repeat, $callback
230 334
231=item $w = EV::timer_ns $after, $repeat, $callback 335=item $w = EV::timer_ns $after, $repeat, $callback
232 336
233Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 337Calls the callback after C<$after> seconds (which may be fractional). If
234the 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
235callback returns. 339value as $after) after the callback returns.
236 340
237This means that the callback would be called roughly after C<$after> 341This means that the callback would be called roughly after C<$after>
238seconds, and then every C<$repeat> seconds. "Roughly" because the time of 342seconds, and then every C<$repeat> seconds. The timer does his best not
239callback 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
240drift. 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.
241 346
242The 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
243in 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
244clock, the timer will nevertheless run (roughly) the same time. 349clock, the timer will nevertheless run (roughly) the same time.
245 350
246The 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.
247 352
248=item $w->set ($after, $repeat) 353=item $w->set ($after, $repeat)
249 354
250Reconfigures the watcher, see the constructor above for details. Can be at 355Reconfigures the watcher, see the constructor above for details. Can be called at
251any time. 356any time.
252 357
253=item $w->again 358=item $w->again
254 359
255Similar 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.
256 363
257If the timer is active and repeating, reset the timeout to occur 364If the timer is active and repeating, reset the timeout to occur
258C<$repeat> seconds after now. 365C<$repeat> seconds after now.
259 366
260If the timer is active and non-repeating, it will be stopped.
261
262If the timer is in active and repeating, start it. 367If the timer is inactive and repeating, start it using the repeat value.
263 368
264Otherwise do nothing. 369Otherwise do nothing.
265 370
266This behaviour is useful when you have a timeout for some IO 371This behaviour is useful when you have a timeout for some IO
267operation. 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
268C<$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
269on the timeout. 374on the timeout.
270 375
376=back
271 377
378
379=head3 PERIODIC WATCHERS - to cron or not to cron?
380
381=over 4
382
272=item $w = EV::periodic $at, $interval, $callback 383=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
273 384
274=item $w = EV::periodic_ns $at, $interval, $callback 385=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
275 386
276Similar 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
277(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.
278 393
279If the C<$interval> is zero, then the callback will be called at the time 394It has three distinct "modes":
280C<$at> if that is in the future, or as soon as possible if it is in the
281past. It will not automatically repeat.
282 395
283If the C<$interval> is nonzero, then the watcher will always be scheduled 396=over 4
284to time out at the next C<$at + N * $interval> time.
285 397
286This can be used to schedule a callback to run at very regular intervals, 398=item * absolute timer ($interval = $reschedule_cb = 0)
287as long as the processing time is less then the interval (otherwise 399
288obviously 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).
289 419
290Another way to think about it (for the mathematically inclined) is that 420Another way to think about it (for the mathematically inclined) is that
291EV::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
292C<$time = $at (mod $interval)>, regardless of any time jumps. 422possible time where C<$time = $at (mod $interval)>, regardless of any time
423jumps.
293 424
294This periodic timer is based on "wallclock time", that is, if the clock 425=item * manual reschedule mode ($reschedule_cb = coderef)
295changes (C<ntp>, C<date -s> etc.), then the timer will nevertheless run at 426
296the specified time. This means it will never drift (it might jitter, but 427In this mode $interval and $at are both being ignored. Instead, each
297it 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
298 458
299The 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.
300 460
301=item $w->set ($at, $interval) 461=item $w->set ($at, $interval, $reschedule_cb)
302 462
303Reconfigures the watcher, see the constructor above for details. Can be at 463Reconfigures the watcher, see the constructor above for details. Can be called at
304any time. 464any time.
305 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
306 476
307=item $w = EV::signal $signal, $callback 477=item $w = EV::signal $signal, $callback
308 478
309=item $w = EV::signal_ns $signal, $callback 479=item $w = EV::signal_ns $signal, $callback
310 480
311Call the callback when $signal is received (the signal can be specified 481Call the callback when $signal is received (the signal can be specified by
312by number or by name, just as with kill or %SIG). 482number or by name, just as with C<kill> or C<%SIG>).
313 483
314EV 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
315component 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,
316and 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
317add/remove callbacks to %SIG, so watch out. 487add/remove callbacks to C<%SIG>, so watch out.
318 488
319You can have as many signal watchers per signal as you want. 489You can have as many signal watchers per signal as you want.
320 490
321The 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.
322 492
323=item $w->set ($signal) 493=item $w->set ($signal)
324 494
325Reconfigures the watcher, see the constructor above for details. Can be at 495Reconfigures the watcher, see the constructor above for details. Can be
496called at any time.
497
498=item $current_signum = $w->signal
499
500=item $old_signum = $w->signal ($new_signal)
501
502Returns the previously set signal (always as a number not name) and
503optionally set a new one.
504
505=back
506
507
508=head3 CHILD WATCHERS - watch out for process status changes
509
510=over 4
511
512=item $w = EV::child $pid, $callback
513
514=item $w = EV::child_ns $pid, $callback
515
516Call the callback when a status change for pid C<$pid> (or any pid if
517C<$pid> is 0) has been received. More precisely: when the process receives
518a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
519changed/zombie children and call the callback.
520
521It is valid (and fully supported) to install a child watcher after a child
522has exited but before the event loop has started its next iteration (for
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).
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
529You can have as many pid watchers per pid as you want, they will all be
530called.
531
532The C<child_ns> variant doesn't start (activate) the newly created watcher.
533
534=item $w->set ($pid)
535
536Reconfigures the watcher, see the constructor above for details. Can be called at
326any time. 537any time.
327 538
539=item $current_pid = $w->pid
328 540
329=item $w = EV::child $pid, $callback 541=item $old_pid = $w->pid ($new_pid)
330 542
331=item $w = EV::child_ns $pid, $callback 543Returns the previously set process id and optionally set a new one.
332 544
333Call the callback when a status change for pid C<$pid> (or any pid 545=item $exit_status = $w->rstatus
334if C<$pid> is 0) has been received. More precisely: when the process
335receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all
336changed/zombie children and call the callback.
337 546
338Unlike all other callbacks, this callback will be called with an 547Return the exit/wait status (as returned by waitpid, see the waitpid entry
339additional third argument which is the exit status. See the C<waitpid> 548in perlfunc).
340function for details.
341 549
342You can have as many pid watchers per pid as you want. 550=item $pid = $w->rpid
343 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
344The C<child_ns> variant doesn't start (activate) the newly created watcher. 579The C<stat_ns> variant doesn't start (activate) the newly created watcher.
345 580
346=item $w->set ($pid) 581=item $w->set ($path, $interval)
347 582
348Reconfigures the watcher, see the constructor above for details. Can be at 583Reconfigures the watcher, see the constructor above for details. Can be
349any time. 584called at any time.
350 585
586=item $current_path = $w->path
587
588=item $old_path = $w->path ($new_path)
589
590Returns the previously set path and optionally set a new one.
591
592=item $current_interval = $w->interval
593
594=item $old_interval = $w->interval ($new_interval)
595
596Returns the previously set interval and optionally set a new one. Can be
597used to query the actual interval used.
598
599=back
600
601
602=head3 IDLE WATCHERS - when you've got nothing better to do...
603
604=over 4
351 605
352=item $w = EV::idle $callback 606=item $w = EV::idle $callback
353 607
354=item $w = EV::idle_ns $callback 608=item $w = EV::idle_ns $callback
355 609
359The process will not block as long as any idle watchers are active, and 613The process will not block as long as any idle watchers are active, and
360they will be called repeatedly until stopped. 614they will be called repeatedly until stopped.
361 615
362The C<idle_ns> variant doesn't start (activate) the newly created watcher. 616The C<idle_ns> variant doesn't start (activate) the newly created watcher.
363 617
618=back
619
620
621=head3 PREPARE WATCHERS - customise your event loop!
622
623=over 4
364 624
365=item $w = EV::prepare $callback 625=item $w = EV::prepare $callback
366 626
367=item $w = EV::prepare_ns $callback 627=item $w = EV::prepare_ns $callback
368 628
371 631
372See the EV::check watcher, below, for explanations and an example. 632See the EV::check watcher, below, for explanations and an example.
373 633
374The C<prepare_ns> variant doesn't start (activate) the newly created watcher. 634The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
375 635
636=back
637
638
639=head3 CHECK WATCHERS - customise your event loop even more!
640
641=over 4
376 642
377=item $w = EV::check $callback 643=item $w = EV::check $callback
378 644
379=item $w = EV::check_ns $callback 645=item $w = EV::check_ns $callback
380 646
392 # do nothing unless active 658 # do nothing unless active
393 $dispatcher->{_event_queue_h} 659 $dispatcher->{_event_queue_h}
394 or return; 660 or return;
395 661
396 # make the dispatcher handle any outstanding stuff 662 # make the dispatcher handle any outstanding stuff
663 ... not shown
397 664
398 # create an IO watcher for each and every socket 665 # create an IO watcher for each and every socket
399 @snmp_watcher = ( 666 @snmp_watcher = (
400 (map { EV::io $_, EV::READ, sub { } } 667 (map { EV::io $_, EV::READ, sub { } }
401 keys %{ $dispatcher->{_descriptors} }), 668 keys %{ $dispatcher->{_descriptors} }),
669
670 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
671 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
672 0, sub { },
402 ); 673 );
403
404 # if there are any timeouts, also create a timer
405 push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { }
406 if $event->[Net::SNMP::Dispatcher::_ACTIVE];
407 }; 674 };
408 675
409The callbacks are irrelevant, the only purpose of those watchers is 676The callbacks are irrelevant (and are not even being called), the
410to wake up the process as soon as one of those events occurs (socket 677only purpose of those watchers is to wake up the process as soon as
411readable, or timer timed out). The corresponding EV::check watcher will then 678one of those events occurs (socket readable, or timer timed out). The
412clean up: 679corresponding EV::check watcher will then clean up:
413 680
414 our $snmp_check = EV::check sub { 681 our $snmp_check = EV::check sub {
415 # destroy all watchers 682 # destroy all watchers
416 @snmp_watcher = (); 683 @snmp_watcher = ();
417 684
418 # make the dispatcher handle any new stuff 685 # make the dispatcher handle any new stuff
686 ... not shown
419 }; 687 };
420 688
421The callbacks of the created watchers will not be called as the watchers 689The callbacks of the created watchers will not be called as the watchers
422are destroyed before this cna happen (remember EV::check gets called 690are destroyed before this cna happen (remember EV::check gets called
423first). 691first).
424 692
425The C<check_ns> variant doesn't start (activate) the newly created watcher. 693The C<check_ns> variant doesn't start (activate) the newly created watcher.
426 694
427=back 695=back
428 696
697
698=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
699
700Fork watchers are called when a C<fork ()> was detected. The invocation
701is done before the event loop blocks next and before C<check> watchers
702are being called, and only in the child after the fork.
703
704=over 4
705
706=item $w = EV::fork $callback
707
708=item $w = EV::fork_ns $callback
709
710Call the callback before the event loop is resumed in the child process
711after a fork.
712
713The C<fork_ns> variant doesn't start (activate) the newly created watcher.
714
715=back
716
717
429=head1 THREADS 718=head1 THREADS
430 719
431Threads are not supported by this in any way. Perl pseudo-threads is evil 720Threads are not supported by this module in any way. Perl pseudo-threads
432stuff and must die. 721is evil stuff and must die. As soon as Perl gains real threads I will work
722on thread support for it.
723
724=head1 FORK
725
726Most of the "improved" event delivering mechanisms of modern operating
727systems have quite a few problems with fork(2) (to put it bluntly: it is
728not supported and usually destructive). Libev makes it possible to work
729around this by having a function that recreates the kernel state after
730fork in the child.
731
732On non-win32 platforms, this module requires the pthread_atfork
733functionality to do this automatically for you. This function is quite
734buggy on most BSDs, though, so YMMV. The overhead for this is quite
735negligible, because everything the function currently does is set a flag
736that is checked only when the event loop gets used the next time, so when
737you do fork but not use EV, the overhead is minimal.
738
739On win32, there is no notion of fork so all this doesn't apply, of course.
433 740
434=cut 741=cut
435 742
436our $DIED = sub { 743our $DIED = sub {
437 warn "EV: error in callback (ignoring): $@"; 744 warn "EV: error in callback (ignoring): $@";
438}; 745};
439 746
440init; 747default_loop
441 748 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?';
442push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
443 749
4441; 7501;
445 751
446=head1 SEE ALSO 752=head1 SEE ALSO
447 753
448 L<EV::DNS>, L<EV::AnyEvent>. 754L<EV::DNS>.
449 755
450=head1 AUTHOR 756=head1 AUTHOR
451 757
452 Marc Lehmann <schmorp@schmorp.de> 758 Marc Lehmann <schmorp@schmorp.de>
453 http://home.schmorp.de/ 759 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines