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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines