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

Comparing EV/EV.pm (file contents):
Revision 1.49 by root, Sat Nov 24 08:28:10 2007 UTC vs.
Revision 1.87 by root, Tue Apr 15 04:41:57 2008 UTC

35 warn "sigquit received\n"; 35 warn "sigquit received\n";
36 }; 36 };
37 37
38 # CHILD/PID STATUS CHANGES 38 # CHILD/PID STATUS CHANGES
39 39
40 my $w = EV::child 666, sub { 40 my $w = EV::child 666, 0, sub {
41 my ($w, $revents) = @_; 41 my ($w, $revents) = @_;
42 my $status = $w->rstatus; 42 my $status = $w->rstatus;
43 };
44
45 # STAT CHANGES
46 my $w = EV::stat "/etc/passwd", 10, sub {
47 my ($w, $revents) = @_;
48 warn $w->path, " has changed somehow.\n";
43 }; 49 };
44 50
45 # MAINLOOP 51 # MAINLOOP
46 EV::loop; # loop until EV::unloop is called or all watchers stop 52 EV::loop; # loop until EV::unloop is called or all watchers stop
47 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
48 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
49 55
50=head1 DESCRIPTION 56=head1 DESCRIPTION
51 57
52This module provides an interface to libev 58This module provides an interface to libev
53(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.
54 65
55=cut 66=cut
56 67
57package EV; 68package EV;
58 69
59use strict; 70use strict;
60 71
61BEGIN { 72BEGIN {
62 our $VERSION = '1.2'; 73 our $VERSION = '3.2';
63 use XSLoader; 74 use XSLoader;
64 XSLoader::load "EV", $VERSION; 75 XSLoader::load "EV", $VERSION;
65} 76}
66 77
67@EV::IO::ISA = 78@EV::IO::ISA =
68@EV::Timer::ISA = 79@EV::Timer::ISA =
69@EV::Periodic::ISA = 80@EV::Periodic::ISA =
70@EV::Signal::ISA = 81@EV::Signal::ISA =
82@EV::Child::ISA =
83@EV::Stat::ISA =
71@EV::Idle::ISA = 84@EV::Idle::ISA =
72@EV::Prepare::ISA = 85@EV::Prepare::ISA =
73@EV::Check::ISA = 86@EV::Check::ISA =
74@EV::Child::ISA = "EV::Watcher"; 87@EV::Embed::ISA =
88@EV::Fork::ISA =
89@EV::Async::ISA =
90 "EV::Watcher";
91
92@EV::Loop::Default::ISA = "EV::Loop";
93
94=head1 EVENT LOOPS
95
96EV supports multiple event loops: There is a single "default event loop"
97that can handle everything including signals and child watchers, and any
98number of "dynamic event loops" that can use different backends (with
99various limitations), but no child and signal watchers.
100
101You do not have to do anything to create the default event loop: When
102the module is loaded a suitable backend is selected on the premise of
103selecting a working backend (which for example rules out kqueue on most
104BSDs). Modules should, unless they have "special needs" always use the
105default loop as this is fastest (perl-wise), best supported by other
106modules (e.g. AnyEvent or Coro) and most portable event loop.
107
108For specific programs you can create additional event loops dynamically.
109
110=over 4
111
112=item $loop = new EV::loop [$flags]
113
114Create a new event loop as per the specified flags. Please refer to the
115C<ev_loop_new ()> function description in the libev documentation
116(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>)
117for more info.
118
119The loop will automatically be destroyed when it is no longer referenced
120by any watcher and the loop object goes out of scope.
121
122Using C<EV::FLAG_FORKCHECK> is recommended, as only the default event loop
123is protected by this module.
124
125=item $loop->loop_fork
126
127Must be called after a fork in the child, before entering or continuing
128the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
129this fucntion automatically, at some performance loss (refer to the libev
130documentation).
131
132=item $loop = EV::default_loop [$flags]
133
134Return the default loop (which is a singleton object).
135
136=back
137
75 138
76=head1 BASIC INTERFACE 139=head1 BASIC INTERFACE
77 140
78=over 4 141=over 4
79 142
80=item $EV::DIED 143=item $EV::DIED
81 144
82Must contain a reference to a function that is called when a callback 145Must contain a reference to a function that is called when a callback
83throws an exception (with $@ containing thr error). The default prints an 146throws an exception (with $@ containing the error). The default prints an
84informative message and continues. 147informative message and continues.
85 148
86If this callback throws an exception it will be silently ignored. 149If this callback throws an exception it will be silently ignored.
87 150
151=item $flags = EV::supported_backends
152
153=item $flags = EV::recommended_backends
154
155=item $flags = EV::embeddable_backends
156
157Returns the set (see C<EV::BACKEND_*> flags) of backends supported by this
158instance of EV, the set of recommended backends (supposed to be good) for
159this platform and the set of embeddable backends (see EMBED WATCHERS).
160
161=item EV::sleep $seconds
162
163Block the process for the given number of (fractional) seconds.
164
88=item $time = EV::time 165=item $time = EV::time
89 166
90Returns the current time in (fractional) seconds since the epoch. 167Returns the current time in (fractional) seconds since the epoch.
91 168
92=item $time = EV::now 169=item $time = EV::now
170
171=item $time = $loop->now
93 172
94Returns the time the last event loop iteration has been started. This 173Returns the time the last event loop iteration has been started. This
95is the time that (relative) timers are based on, and refering to it is 174is the time that (relative) timers are based on, and refering to it is
96usually faster then calling EV::time. 175usually faster then calling EV::time.
97 176
98=item $method = EV::method 177=item $backend = EV::backend
178
179=item $backend = $loop->backend
99 180
100Returns an integer describing the backend used by libev (EV::METHOD_SELECT 181Returns an integer describing the backend used by libev (EV::METHOD_SELECT
101or EV::METHOD_EPOLL). 182or EV::METHOD_EPOLL).
102 183
103=item EV::loop [$flags] 184=item EV::loop [$flags]
185
186=item $loop->loop ([$flags])
104 187
105Begin checking for events and calling callbacks. It returns when a 188Begin checking for events and calling callbacks. It returns when a
106callback calls EV::unloop. 189callback calls EV::unloop.
107 190
108The $flags argument can be one of the following: 191The $flags argument can be one of the following:
111 EV::LOOP_ONESHOT block at most once (wait, but do not loop) 194 EV::LOOP_ONESHOT block at most once (wait, but do not loop)
112 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) 195 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)
113 196
114=item EV::unloop [$how] 197=item EV::unloop [$how]
115 198
199=item $loop->unloop ([$how])
200
116When called with no arguments or an argument of EV::UNLOOP_ONE, makes the 201When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
117innermost call to EV::loop return. 202innermost call to EV::loop return.
118 203
119When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as 204When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
120fast as possible. 205fast as possible.
121 206
207=item $count = EV::loop_count
208
209=item $count = $loop->loop_count
210
211Return the number of times the event loop has polled for new
212events. Sometiems useful as a generation counter.
213
122=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) 214=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
215
216=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
123 217
124This function rolls together an I/O and a timer watcher for a single 218This function rolls together an I/O and a timer watcher for a single
125one-shot event without the need for managing a watcher object. 219one-shot event without the need for managing a watcher object.
126 220
127If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events> 221If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
133If timeout is C<undef> or negative, then there will be no 227If timeout is C<undef> or negative, then there will be no
134timeout. Otherwise a EV::timer with this value will be started. 228timeout. Otherwise a EV::timer with this value will be started.
135 229
136When an error occurs or either the timeout or I/O watcher triggers, then 230When an error occurs or either the timeout or I/O watcher triggers, then
137the callback will be called with the received event set (in general 231the callback will be called with the received event set (in general
138you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>, 232you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>,
139C<EV::WRITE> and C<EV::TIMEOUT>). 233C<EV::WRITE> and C<EV::TIMEOUT>).
140 234
141EV::once doesn't return anything: the watchers stay active till either 235EV::once doesn't return anything: the watchers stay active till either
142of them triggers, then they will be stopped and freed, and the callback 236of them triggers, then they will be stopped and freed, and the callback
143invoked. 237invoked.
144 238
145=back 239=item EV::feed_fd_event ($fd, $revents)
146 240
147=head2 WATCHER 241=item $loop->feed_fd_event ($fd, $revents)
242
243Feed an event on a file descriptor into EV. EV will react to this call as
244if the readyness notifications specified by C<$revents> (a combination of
245C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
246
247=item EV::feed_signal_event ($signal)
248
249Feed a signal event into EV. EV will react to this call as if the signal
250specified by C<$signal> had occured.
251
252=item EV::set_io_collect_interval $time
253
254=item $loop->set_io_collect_interval ($time)
255
256=item EV::set_timeout_collect_interval $time
257
258=item $loop->set_timeout_collect_interval ($time)
259
260These advanced functions set the minimum block interval when polling for I/O events and the minimum
261wait interval for timer events. See the libev documentation at
262L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> for
263a more detailed discussion.
264
265=back
266
267
268=head1 WATCHER OBJECTS
148 269
149A watcher is an object that gets created to record your interest in some 270A watcher is an object that gets created to record your interest in some
150event. For instance, if you want to wait for STDIN to become readable, you 271event. For instance, if you want to wait for STDIN to become readable, you
151would create an EV::io watcher for that: 272would create an EV::io watcher for that:
152 273
153 my $watcher = EV::io *STDIN, EV::READ, sub { 274 my $watcher = EV::io *STDIN, EV::READ, sub {
154 my ($watcher, $revents) = @_; 275 my ($watcher, $revents) = @_;
155 warn "yeah, STDIN should not be readable without blocking!\n" 276 warn "yeah, STDIN should now be readable without blocking!\n"
156 }; 277 };
157 278
158All watchers can be active (waiting for events) or inactive (paused). Only 279All watchers can be active (waiting for events) or inactive (paused). Only
159active watchers will have their callbacks invoked. All callbacks will be 280active watchers will have their callbacks invoked. All callbacks will be
160called with at least two arguments: the watcher and a bitmask of received 281called with at least two arguments: the watcher and a bitmask of received
161events. 282events.
162 283
163Each watcher type has its associated bit in revents, so you can use the 284Each watcher type has its associated bit in revents, so you can use the
164same callback for multiple watchers. The event mask is named after the 285same callback for multiple watchers. The event mask is named after the
165type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, 286type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
166EV::periodic sets EV::PERIODIC and so on, with the exception of IO events 287EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
167(which can set both EV::READ and EV::WRITE bits), and EV::timer (which 288(which can set both EV::READ and EV::WRITE bits), and EV::timer (which
168uses EV::TIMEOUT). 289uses EV::TIMEOUT).
169 290
170In the rare case where one wants to create a watcher but not start it at 291In the rare case where one wants to create a watcher but not start it at
171the same time, each constructor has a variant with a trailing C<_ns> in 292the same time, each constructor has a variant with a trailing C<_ns> in
177 298
178Also, all methods changing some aspect of a watcher (->set, ->priority, 299Also, all methods changing some aspect of a watcher (->set, ->priority,
179->fh and so on) automatically stop and start it again if it is active, 300->fh and so on) automatically stop and start it again if it is active,
180which means pending events get lost. 301which means pending events get lost.
181 302
182=head2 WATCHER TYPES 303=head2 COMMON WATCHER METHODS
183 304
184Now lets move to the existing watcher types and asociated methods. 305This section lists methods common to all watchers.
185
186The following methods are available for all watchers. Then followes a
187description of each watcher constructor (EV::io, EV::timer, EV::periodic,
188EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by
189any type-specific methods (if any).
190 306
191=over 4 307=over 4
192 308
193=item $w->start 309=item $w->start
194 310
198 314
199=item $w->stop 315=item $w->stop
200 316
201Stop a watcher if it is active. Also clear any pending events (events that 317Stop a watcher if it is active. Also clear any pending events (events that
202have been received but that didn't yet result in a callback invocation), 318have been received but that didn't yet result in a callback invocation),
203regardless of wether the watcher was active or not. 319regardless of whether the watcher was active or not.
204 320
205=item $bool = $w->is_active 321=item $bool = $w->is_active
206 322
207Returns true if the watcher is active, false otherwise. 323Returns true if the watcher is active, false otherwise.
208 324
233watchers with higher priority will be invoked first. The valid range of 349watchers with higher priority will be invoked first. The valid range of
234priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default 350priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
235-2). If the priority is outside this range it will automatically be 351-2). If the priority is outside this range it will automatically be
236normalised to the nearest valid priority. 352normalised to the nearest valid priority.
237 353
238The default priority of any newly-created weatcher is 0. 354The default priority of any newly-created watcher is 0.
239 355
356Note that the priority semantics have not yet been fleshed out and are
357subject to almost certain change.
358
240=item $w->trigger ($revents) 359=item $w->invoke ($revents)
241 360
242Call the callback *now* with the given event mask. 361Call the callback *now* with the given event mask.
243 362
363=item $w->feed_event ($revents)
364
365Feed some events on this watcher into EV. EV will react to this call as if
366the watcher had received the given C<$revents> mask.
367
368=item $revents = $w->clear_pending
369
370If the watcher is pending, this function clears its pending status and
371returns its C<$revents> bitset (as if its callback was invoked). If the
372watcher isn't pending it does nothing and returns C<0>.
373
374=item $previous_state = $w->keepalive ($bool)
375
376Normally, C<EV::loop> will return when there are no active watchers
377(which is a "deadlock" because no progress can be made anymore). This is
378convinient because it allows you to start your watchers (and your jobs),
379call C<EV::loop> once and when it returns you know that all your jobs are
380finished (or they forgot to register some watchers for their task :).
381
382Sometimes, however, this gets in your way, for example when the module
383that calls C<EV::loop> (usually the main program) is not the same module
384as a long-living watcher (for example a DNS client module written by
385somebody else even). Then you might want any outstanding requests to be
386handled, but you would not want to keep C<EV::loop> from returning just
387because you happen to have this long-running UDP port watcher.
388
389In this case you can clear the keepalive status, which means that even
390though your watcher is active, it won't keep C<EV::loop> from returning.
391
392The initial value for keepalive is true (enabled), and you cna change it
393any time.
394
395Example: Register an I/O watcher for some UDP socket but do not keep the
396event loop from running just because of that watcher.
397
398 my $udp_socket = ...
399 my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... };
400 $1000udp_watcher->keepalive (0);
401
402=item $loop = $w->loop
403
404Return the loop that this watcher is attached to.
405
406=back
407
408
409=head1 WATCHER TYPES
410
411Each of the following subsections describes a single watcher type.
412
413=head3 I/O WATCHERS - is this file descriptor readable or writable?
414
415=over 4
244 416
245=item $w = EV::io $fileno_or_fh, $eventmask, $callback 417=item $w = EV::io $fileno_or_fh, $eventmask, $callback
246 418
247=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 419=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
248 420
421=item $w = $loop->io ($fileno_or_fh, $eventmask, $callback)
422
423=item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback)
424
249As long as the returned watcher object is alive, call the C<$callback> 425As long as the returned watcher object is alive, call the C<$callback>
250when the events specified in C<$eventmask>. 426when at least one of events specified in C<$eventmask> occurs.
251 427
252The $eventmask can be one or more of these constants ORed together: 428The $eventmask can be one or more of these constants ORed together:
253 429
254 EV::READ wait until read() wouldn't block anymore 430 EV::READ wait until read() wouldn't block anymore
255 EV::WRITE wait until write() wouldn't block anymore 431 EV::WRITE wait until write() wouldn't block anymore
271 447
272=item $old_eventmask = $w->events ($new_eventmask) 448=item $old_eventmask = $w->events ($new_eventmask)
273 449
274Returns the previously set event mask and optionally set a new one. 450Returns the previously set event mask and optionally set a new one.
275 451
452=back
453
454
455=head3 TIMER WATCHERS - relative and optionally repeating timeouts
456
457=over 4
276 458
277=item $w = EV::timer $after, $repeat, $callback 459=item $w = EV::timer $after, $repeat, $callback
278 460
279=item $w = EV::timer_ns $after, $repeat, $callback 461=item $w = EV::timer_ns $after, $repeat, $callback
280 462
281Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 463=item $w = $loop->timer ($after, $repeat, $callback)
282the timer will be restarted (with the $repeat value as $after) after the 464
283callback returns. 465=item $w = $loop->timer_ns ($after, $repeat, $callback)
466
467Calls the callback after C<$after> seconds (which may be fractional). If
468C<$repeat> is non-zero, the timer will be restarted (with the $repeat
469value as $after) after the callback returns.
284 470
285This means that the callback would be called roughly after C<$after> 471This means that the callback would be called roughly after C<$after>
286seconds, and then every C<$repeat> seconds. The timer does his best not 472seconds, and then every C<$repeat> seconds. The timer does his best not
287to drift, but it will not invoke the timer more often then once per event 473to drift, but it will not invoke the timer more often then once per event
288loop iteration, and might drift in other cases. If that isn't acceptable, 474loop iteration, and might drift in other cases. If that isn't acceptable,
294 480
295The C<timer_ns> variant doesn't start (activate) the newly created watcher. 481The C<timer_ns> variant doesn't start (activate) the newly created watcher.
296 482
297=item $w->set ($after, $repeat) 483=item $w->set ($after, $repeat)
298 484
299Reconfigures the watcher, see the constructor above for details. Can be at 485Reconfigures the watcher, see the constructor above for details. Can be called at
300any time. 486any time.
301 487
302=item $w->again 488=item $w->again
303 489
304Similar to the C<start> method, but has special semantics for repeating timers: 490Similar to the C<start> method, but has special semantics for repeating timers:
315This behaviour is useful when you have a timeout for some IO 501This behaviour is useful when you have a timeout for some IO
316operation. You create a timer object with the same value for C<$after> and 502operation. You create a timer object with the same value for C<$after> and
317C<$repeat>, and then, in the read/write watcher, run the C<again> method 503C<$repeat>, and then, in the read/write watcher, run the C<again> method
318on the timeout. 504on the timeout.
319 505
506=back
507
508
509=head3 PERIODIC WATCHERS - to cron or not to cron?
510
511=over 4
320 512
321=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback 513=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
322 514
323=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback 515=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
516
517=item $w = $loop->periodic ($at, $interval, $reschedule_cb, $callback)
518
519=item $w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback)
324 520
325Similar to EV::timer, but is not based on relative timeouts but on 521Similar to EV::timer, but is not based on relative timeouts but on
326absolute times. Apart from creating "simple" timers that trigger "at" the 522absolute times. Apart from creating "simple" timers that trigger "at" the
327specified time, it can also be used for non-drifting absolute timers and 523specified time, it can also be used for non-drifting absolute timers and
328more complex, cron-like, setups that are not adversely affected by time 524more complex, cron-like, setups that are not adversely affected by time
338This time simply fires at the wallclock time C<$at> and doesn't repeat. It 534This time simply fires at the wallclock time C<$at> and doesn't repeat. It
339will not adjust when a time jump occurs, that is, if it is to be run 535will not adjust when a time jump occurs, that is, if it is to be run
340at January 1st 2011 then it will run when the system time reaches or 536at January 1st 2011 then it will run when the system time reaches or
341surpasses this time. 537surpasses this time.
342 538
343=item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0) 539=item * repeating interval timer ($interval > 0, $reschedule_cb = 0)
344 540
345In this mode the watcher will always be scheduled to time out at the 541In this mode the watcher will always be scheduled to time out at the
346next C<$at + N * $interval> time (for some integer N) and then repeat, 542next C<$at + N * $interval> time (for some integer N) and then repeat,
347regardless of any time jumps. 543regardless of any time jumps.
348 544
396 592
397The C<periodic_ns> variant doesn't start (activate) the newly created watcher. 593The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
398 594
399=item $w->set ($at, $interval, $reschedule_cb) 595=item $w->set ($at, $interval, $reschedule_cb)
400 596
401Reconfigures the watcher, see the constructor above for details. Can be at 597Reconfigures the watcher, see the constructor above for details. Can be called at
402any time. 598any time.
403 599
404=item $w->again 600=item $w->again
405 601
406Simply stops and starts the watcher again. 602Simply stops and starts the watcher again.
407 603
604=item $time = $w->at
605
606Return the time that the watcher is expected to trigger next.
607
608=back
609
610
611=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
612
613=over 4
408 614
409=item $w = EV::signal $signal, $callback 615=item $w = EV::signal $signal, $callback
410 616
411=item $w = EV::signal_ns $signal, $callback 617=item $w = EV::signal_ns $signal, $callback
412 618
413Call the callback when $signal is received (the signal can be specified 619Call the callback when $signal is received (the signal can be specified by
414by number or by name, just as with kill or %SIG). 620number or by name, just as with C<kill> or C<%SIG>).
415 621
416EV will grab the signal for the process (the kernel only allows one 622EV will grab the signal for the process (the kernel only allows one
417component to receive a signal at a time) when you start a signal watcher, 623component to receive a signal at a time) when you start a signal watcher,
418and removes it again when you stop it. Perl does the same when you 624and removes it again when you stop it. Perl does the same when you
419add/remove callbacks to %SIG, so watch out. 625add/remove callbacks to C<%SIG>, so watch out.
420 626
421You can have as many signal watchers per signal as you want. 627You can have as many signal watchers per signal as you want.
422 628
423The C<signal_ns> variant doesn't start (activate) the newly created watcher. 629The C<signal_ns> variant doesn't start (activate) the newly created watcher.
424 630
425=item $w->set ($signal) 631=item $w->set ($signal)
426 632
427Reconfigures the watcher, see the constructor above for details. Can be at 633Reconfigures the watcher, see the constructor above for details. Can be
428any time. 634called at any time.
429 635
430=item $current_signum = $w->signal 636=item $current_signum = $w->signal
431 637
432=item $old_signum = $w->signal ($new_signal) 638=item $old_signum = $w->signal ($new_signal)
433 639
434Returns the previously set signal (always as a number not name) and 640Returns the previously set signal (always as a number not name) and
435optionally set a new one. 641optionally set a new one.
436 642
643=back
437 644
645
646=head3 CHILD WATCHERS - watch out for process status changes
647
648=over 4
649
438=item $w = EV::child $pid, $callback 650=item $w = EV::child $pid, $trace, $callback
439 651
440=item $w = EV::child_ns $pid, $callback 652=item $w = EV::child_ns $pid, $trace, $callback
653
654=item $w = $loop->child ($pid, $trace, $callback)
655
656=item $w = $loop->child_ns ($pid, $trace, $callback)
441 657
442Call the callback when a status change for pid C<$pid> (or any pid 658Call the callback when a status change for pid C<$pid> (or any pid
443if C<$pid> is 0) has been received. More precisely: when the process 659if C<$pid> is 0) has been received (a status change happens when the
660process terminates or is killed, or, when trace is true, additionally when
661it is stopped or continued). More precisely: when the process receives
444receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all 662a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
445changed/zombie children and call the callback. 663changed/zombie children and call the callback.
446 664
447You can access both status and pid by using the C<rstatus> and C<rpid> 665It is valid (and fully supported) to install a child watcher after a child
448methods on the watcher object. 666has exited but before the event loop has started its next iteration (for
667example, first you C<fork>, then the new child process might exit, and
668only then do you install a child watcher in the parent for the new pid).
449 669
670You can access both exit (or tracing) status and pid by using the
671C<rstatus> and C<rpid> methods on the watcher object.
672
450You can have as many pid watchers per pid as you want. 673You can have as many pid watchers per pid as you want, they will all be
674called.
451 675
452The C<child_ns> variant doesn't start (activate) the newly created watcher. 676The C<child_ns> variant doesn't start (activate) the newly created watcher.
453 677
454=item $w->set ($pid) 678=item $w->set ($pid, $trace)
455 679
456Reconfigures the watcher, see the constructor above for details. Can be at 680Reconfigures the watcher, see the constructor above for details. Can be called at
457any time. 681any time.
458 682
459=item $current_pid = $w->pid 683=item $current_pid = $w->pid
460
461=item $old_pid = $w->pid ($new_pid)
462 684
463Returns the previously set process id and optionally set a new one. 685Returns the previously set process id and optionally set a new one.
464 686
465=item $exit_status = $w->rstatus 687=item $exit_status = $w->rstatus
466 688
470=item $pid = $w->rpid 692=item $pid = $w->rpid
471 693
472Return the pid of the awaited child (useful when you have installed a 694Return the pid of the awaited child (useful when you have installed a
473watcher for all pids). 695watcher for all pids).
474 696
697=back
698
699
700=head3 STAT WATCHERS - did the file attributes just change?
701
702=over 4
703
704=item $w = EV::stat $path, $interval, $callback
705
706=item $w = EV::stat_ns $path, $interval, $callback
707
708=item $w = $loop->stat ($path, $interval, $callback)
709
710=item $w = $loop->stat_ns ($path, $interval, $callback)
711
712Call the callback when a file status change has been detected on
713C<$path>. The C<$path> does not need to exist, changing from "path exists"
714to "path does not exist" is a status change like any other.
715
716The C<$interval> is a recommended polling interval for systems where
717OS-supported change notifications don't exist or are not supported. If
718you use C<0> then an unspecified default is used (which is highly
719recommended!), which is to be expected to be around five seconds usually.
720
721This watcher type is not meant for massive numbers of stat watchers,
722as even with OS-supported change notifications, this can be
723resource-intensive.
724
725The C<stat_ns> variant doesn't start (activate) the newly created watcher.
726
727=item ... = $w->stat
728
729This call is very similar to the perl C<stat> built-in: It stats (using
730C<lstat>) the path specified in the watcher and sets perls stat cache (as
731well as EV's idea of the current stat values) to the values found.
732
733In scalar context, a boolean is return indicating success or failure of
734the stat. In list context, the same 13-value list as with stat is returned
735(except that the blksize and blocks fields are not reliable).
736
737In the case of an error, errno is set to C<ENOENT> (regardless of the
738actual error value) and the C<nlink> value is forced to zero (if the stat
739was successful then nlink is guaranteed to be non-zero).
740
741See also the next two entries for more info.
742
743=item ... = $w->attr
744
745Just like C<< $w->stat >>, but without the initial stat'ing: this returns
746the values most recently detected by EV. See the next entry for more info.
747
748=item ... = $w->prev
749
750Just like C<< $w->stat >>, but without the initial stat'ing: this returns
751the previous set of values, before the change.
752
753That is, when the watcher callback is invoked, C<< $w->prev >> will be set
754to the values found I<before> a change was detected, while C<< $w->attr >>
755returns the values found leading to the change detection. The difference (if any)
756between C<prev> and C<attr> is what triggered the callback.
757
758If you did something to the filesystem object and do not want to trigger
759yet another change, you can call C<stat> to update EV's idea of what the
760current attributes are.
761
762=item $w->set ($path, $interval)
763
764Reconfigures the watcher, see the constructor above for details. Can be
765called at any time.
766
767=item $current_path = $w->path
768
769=item $old_path = $w->path ($new_path)
770
771Returns the previously set path and optionally set a new one.
772
773=item $current_interval = $w->interval
774
775=item $old_interval = $w->interval ($new_interval)
776
777Returns the previously set interval and optionally set a new one. Can be
778used to query the actual interval used.
779
780=back
781
782
783=head3 IDLE WATCHERS - when you've got nothing better to do...
784
785=over 4
475 786
476=item $w = EV::idle $callback 787=item $w = EV::idle $callback
477 788
478=item $w = EV::idle_ns $callback 789=item $w = EV::idle_ns $callback
479 790
480Call the callback when there are no pending io, timer/periodic, signal or 791=item $w = $loop->idle ($callback)
481child events, i.e. when the process is idle. 792
793=item $w = $loop->idle_ns ($callback)
794
795Call the callback when there are no other pending watchers of the same or
796higher priority (excluding check, prepare and other idle watchers of the
797same or lower priority, of course). They are called idle watchers because
798when the watcher is the highest priority pending event in the process, the
799process is considered to be idle at that priority.
800
801If you want a watcher that is only ever called when I<no> other events are
802outstanding you have to set the priority to C<EV::MINPRI>.
482 803
483The process will not block as long as any idle watchers are active, and 804The process will not block as long as any idle watchers are active, and
484they will be called repeatedly until stopped. 805they will be called repeatedly until stopped.
485 806
807For example, if you have idle watchers at priority C<0> and C<1>, and
808an I/O watcher at priority C<0>, then the idle watcher at priority C<1>
809and the I/O watcher will always run when ready. Only when the idle watcher
810at priority C<1> is stopped and the I/O watcher at priority C<0> is not
811pending with the C<0>-priority idle watcher be invoked.
812
486The C<idle_ns> variant doesn't start (activate) the newly created watcher. 813The C<idle_ns> variant doesn't start (activate) the newly created watcher.
487 814
815=back
816
817
818=head3 PREPARE WATCHERS - customise your event loop!
819
820=over 4
488 821
489=item $w = EV::prepare $callback 822=item $w = EV::prepare $callback
490 823
491=item $w = EV::prepare_ns $callback 824=item $w = EV::prepare_ns $callback
825
826=item $w = $loop->prepare ($callback)
827
828=item $w = $loop->prepare_ns ($callback)
492 829
493Call the callback just before the process would block. You can still 830Call the callback just before the process would block. You can still
494create/modify any watchers at this point. 831create/modify any watchers at this point.
495 832
496See the EV::check watcher, below, for explanations and an example. 833See the EV::check watcher, below, for explanations and an example.
497 834
498The C<prepare_ns> variant doesn't start (activate) the newly created watcher. 835The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
499 836
837=back
838
839
840=head3 CHECK WATCHERS - customise your event loop even more!
841
842=over 4
500 843
501=item $w = EV::check $callback 844=item $w = EV::check $callback
502 845
503=item $w = EV::check_ns $callback 846=item $w = EV::check_ns $callback
847
848=item $w = $loop->check ($callback)
849
850=item $w = $loop->check_ns ($callback)
504 851
505Call the callback just after the process wakes up again (after it has 852Call the callback just after the process wakes up again (after it has
506gathered events), but before any other callbacks have been invoked. 853gathered events), but before any other callbacks have been invoked.
507 854
508This is used to integrate other event-based software into the EV 855This is used to integrate other event-based software into the EV
518 or return; 865 or return;
519 866
520 # make the dispatcher handle any outstanding stuff 867 # make the dispatcher handle any outstanding stuff
521 ... not shown 868 ... not shown
522 869
523 # create an IO watcher for each and every socket 870 # create an I/O watcher for each and every socket
524 @snmp_watcher = ( 871 @snmp_watcher = (
525 (map { EV::io $_, EV::READ, sub { } } 872 (map { EV::io $_, EV::READ, sub { } }
526 keys %{ $dispatcher->{_descriptors} }), 873 keys %{ $dispatcher->{_descriptors} }),
527 874
528 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] 875 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
549first). 896first).
550 897
551The C<check_ns> variant doesn't start (activate) the newly created watcher. 898The C<check_ns> variant doesn't start (activate) the newly created watcher.
552 899
553=back 900=back
901
902
903=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
904
905Fork watchers are called when a C<fork ()> was detected. The invocation
906is done before the event loop blocks next and before C<check> watchers
907are being called, and only in the child after the fork.
908
909=over 4
910
911=item $w = EV::fork $callback
912
913=item $w = EV::fork_ns $callback
914
915=item $w = $loop->fork ($callback)
916
917=item $w = $loop->fork_ns ($callback)
918
919Call the callback before the event loop is resumed in the child process
920after a fork.
921
922The C<fork_ns> variant doesn't start (activate) the newly created watcher.
923
924=back
925
926
927=head3 EMBED WATCHERS - when one backend isn't enough...
928
929This is a rather advanced watcher type that lets you embed one event loop
930into another (currently only IO events are supported in the embedded
931loop, other types of watchers might be handled in a delayed or incorrect
932fashion and must not be used).
933
934See the libev documentation at
935L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_>
936for more details.
937
938In short, this watcher is most useful on BSD systems without working
939kqueue to still be able to handle a large number of sockets:
940
941 my $socket_loop;
942
943 # check wether we use SELECT or POLL _and_ KQUEUE is supported
944 if (
945 (EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT))
946 && (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE)
947 ) {
948 # use kqueue for sockets
949 $socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV;
950 }
951
952 # use the default loop otherwise
953 $socket_loop ||= EV::default_loop;
954
955=over 4
956
957=item $w = EV::embed $otherloop, $callback
958
959=item $w = EV::embed_ns $otherloop, $callback
960
961=item $w = $loop->embed ($otherloop, $callback)
962
963=item $w = $loop->embed_ns ($otherloop, $callback)
964
965Call the callback when the embedded event loop (C<$otherloop>) has any
966I/O activity. The C<$callback> should alwas be specified as C<undef> in
967this version of EV, which means the embedded event loop will be managed
968automatically.
969
970The C<embed_ns> variant doesn't start (activate) the newly created watcher.
971
972=back
973
974=head3 ASYNC WATCHERS - how to wake up another event loop
975
976Async watchers are provided by EV, but have little use in perl directly, as perl
977neither supports threads nor direct access to signal handlers or other
978contexts where they could be of value.
979
980It is, however, possible to use them from the XS level.
981
982Please see the libev documentation for further details.
983
984=over 4
985
986=item $w = EV::async $callback
987
988=item $w = EV::async_ns $callback
989
990=item $w->send
991
992=item $bool = $w->async_pending
993
994=back
995
996
997=head1 PERL SIGNALS
998
999While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
1000with EV is as the same as any other C library: Perl-signals will only be
1001handled when Perl runs, which means your signal handler might be invoked
1002only the next time an event callback is invoked.
1003
1004The solution is to use EV signal watchers (see C<EV::signal>), which will
1005ensure proper operations with regards to other event watchers.
1006
1007If you cannot do this for whatever reason, you can also force a watcher
1008to be called on every event loop iteration by installing a C<EV::check>
1009watcher:
1010
1011 my $async_check = EV::check sub { };
1012
1013This ensures that perl gets into control for a short time to handle any
1014pending signals, and also ensures (slightly) slower overall operation.
554 1015
555=head1 THREADS 1016=head1 THREADS
556 1017
557Threads are not supported by this module in any way. Perl pseudo-threads 1018Threads are not supported by this module in any way. Perl pseudo-threads
558is evil stuff and must die. As soon as Perl gains real threads I will work 1019is evil stuff and must die. As soon as Perl gains real threads I will work
580our $DIED = sub { 1041our $DIED = sub {
581 warn "EV: error in callback (ignoring): $@"; 1042 warn "EV: error in callback (ignoring): $@";
582}; 1043};
583 1044
584default_loop 1045default_loop
585 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?'; 1046 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_FLAGS}?';
586 1047
5871; 10481;
588 1049
589=head1 SEE ALSO 1050=head1 SEE ALSO
590 1051
591 L<EV::DNS>. 1052L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as
1053event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient
1054coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP).
592 1055
593=head1 AUTHOR 1056=head1 AUTHOR
594 1057
595 Marc Lehmann <schmorp@schmorp.de> 1058 Marc Lehmann <schmorp@schmorp.de>
596 http://home.schmorp.de/ 1059 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines