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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines