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

Comparing EV/EV.pm (file contents):
Revision 1.25 by root, Fri Nov 2 22:18:49 2007 UTC vs.
Revision 1.49 by root, Sat Nov 24 08:28:10 2007 UTC

10 10
11 my $w = EV::timer 2, 0, sub { 11 my $w = EV::timer 2, 0, sub {
12 warn "is called after 2s"; 12 warn "is called after 2s";
13 }; 13 };
14 14
15 my $w = EV::timer 2, 1, sub { 15 my $w = EV::timer 2, 2, sub {
16 warn "is called roughly every 2s (repeat = 1)"; 16 warn "is called roughly every 2s (repeat = 2)";
17 }; 17 };
18 18
19 undef $w; # destroy event watcher again 19 undef $w; # destroy event watcher again
20 20
21 my $w = EV::periodic 0, 60, sub { 21 my $w = EV::periodic 0, 60, 0, sub {
22 warn "is called every minute, on the minute, exactly"; 22 warn "is called every minute, on the minute, exactly";
23 }; 23 };
24 24
25 # IO 25 # IO
26 26
27 my $w = EV::io *STDIN, EV::READ, sub { 27 my $w = EV::io *STDIN, EV::READ, sub {
28 my ($w, $revents) = @_; # all callbacks get the watcher object and event mask 28 my ($w, $revents) = @_; # all callbacks receive the watcher and event mask
29 warn "stdin is readable, you entered: ", <STDIN>; 29 warn "stdin is readable, you entered: ", <STDIN>;
30 }; 30 };
31 31
32 # SIGNALS 32 # SIGNALS
33 33
34 my $w = EV::signal 'QUIT', sub { 34 my $w = EV::signal 'QUIT', sub {
35 warn "sigquit received\n"; 35 warn "sigquit received\n";
36 }; 36 };
37 37
38 my $w = EV::signal 3, sub {
39 warn "sigquit received (this is GNU/Linux, right?)\n";
40 };
41
42 # CHILD/PID STATUS CHANGES 38 # CHILD/PID STATUS CHANGES
43 39
44 my $w = EV::child 666, sub { 40 my $w = EV::child 666, sub {
45 my ($w, $revents, $status) = @_; 41 my ($w, $revents) = @_;
42 my $status = $w->rstatus;
46 }; 43 };
47 44
48 # MAINLOOP 45 # MAINLOOP
49 EV::loop; # loop until EV::loop_done is called 46 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 47 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 48 EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block
52 49
53=head1 DESCRIPTION 50=head1 DESCRIPTION
54 51
60package EV; 57package EV;
61 58
62use strict; 59use strict;
63 60
64BEGIN { 61BEGIN {
65 our $VERSION = '0.5'; 62 our $VERSION = '1.2';
66 use XSLoader; 63 use XSLoader;
67 XSLoader::load "EV", $VERSION; 64 XSLoader::load "EV", $VERSION;
68} 65}
69 66
70@EV::Io::ISA = 67@EV::IO::ISA =
71@EV::Timer::ISA = 68@EV::Timer::ISA =
72@EV::Periodic::ISA = 69@EV::Periodic::ISA =
73@EV::Signal::ISA = 70@EV::Signal::ISA =
74@EV::Idle::ISA = 71@EV::Idle::ISA =
75@EV::Prepare::ISA = 72@EV::Prepare::ISA =
96 93
97Returns the time the last event loop iteration has been started. This 94Returns 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 95is the time that (relative) timers are based on, and refering to it is
99usually faster then calling EV::time. 96usually faster then calling EV::time.
100 97
101=item $method = EV::ev_method 98=item $method = EV::method
102 99
103Returns an integer describing the backend used by libev (EV::METHOD_SELECT 100Returns an integer describing the backend used by libev (EV::METHOD_SELECT
104or EV::METHOD_EPOLL). 101or EV::METHOD_EPOLL).
105 102
106=item EV::loop [$flags] 103=item EV::loop [$flags]
107 104
108Begin checking for events and calling callbacks. It returns when a 105Begin checking for events and calling callbacks. It returns when a
109callback calls EV::loop_done. 106callback calls EV::unloop.
110 107
111The $flags argument can be one of the following: 108The $flags argument can be one of the following:
112 109
113 0 as above 110 0 as above
114 EV::LOOP_ONESHOT block at most once (wait, but do not loop) 111 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) 112 EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)
116 113
117=item EV::loop_done [$how] 114=item EV::unloop [$how]
118 115
119When called with no arguments or an argument of 1, makes the innermost 116When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
120call to EV::loop return. 117innermost call to EV::loop return.
121 118
122When called with an agrument of 2, all calls to EV::loop will return as 119When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
123fast as possible. 120fast as possible.
121
122=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
123
124This function rolls together an I/O and a timer watcher for a single
125one-shot event without the need for managing a watcher object.
126
127If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
128must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
129| EV::WRITE>, indicating the type of I/O event you want to wait for. If
130you do not want to wait for some I/O event, specify C<undef> for
131C<$fh_or_undef> and C<0> for C<$events>).
132
133If timeout is C<undef> or negative, then there will be no
134timeout. Otherwise a EV::timer with this value will be started.
135
136When 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
138you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>,
139C<EV::WRITE> and C<EV::TIMEOUT>).
140
141EV::once doesn't return anything: the watchers stay active till either
142of them triggers, then they will be stopped and freed, and the callback
143invoked.
124 144
125=back 145=back
126 146
127=head2 WATCHER 147=head2 WATCHER
128 148
184 204
185=item $bool = $w->is_active 205=item $bool = $w->is_active
186 206
187Returns true if the watcher is active, false otherwise. 207Returns true if the watcher is active, false otherwise.
188 208
209=item $current_data = $w->data
210
211=item $old_data = $w->data ($new_data)
212
213Queries a freely usable data scalar on the watcher and optionally changes
214it. This is a way to associate custom data with a watcher:
215
216 my $w = EV::timer 60, 0, sub {
217 warn $_[0]->data;
218 };
219 $w->data ("print me!");
220
189=item $current_cb = $w->cb 221=item $current_cb = $w->cb
190 222
191=item $old_cb = $w->cb ($new_cb) 223=item $old_cb = $w->cb ($new_cb)
192 224
193Queries the callback on the watcher and optionally changes it. You can do 225Queries the callback on the watcher and optionally changes it. You can do
249Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, 281Calls the callback after C<$after> seconds. If C<$repeat> is non-zero,
250the timer will be restarted (with the $repeat value as $after) after the 282the timer will be restarted (with the $repeat value as $after) after the
251callback returns. 283callback returns.
252 284
253This means that the callback would be called roughly after C<$after> 285This means that the callback would be called roughly after C<$after>
254seconds, and then every C<$repeat> seconds. "Roughly" because the time of 286seconds, and then every C<$repeat> seconds. The timer does his best not
255callback processing is not taken into account, so the timer will slowly 287to drift, but it will not invoke the timer more often then once per event
256drift. If that isn't acceptable, look at EV::periodic. 288loop iteration, and might drift in other cases. If that isn't acceptable,
289look at EV::periodic, which can provide long-term stable timers.
257 290
258The timer is based on a monotonic clock, that is if somebody is sitting 291The 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 292in front of the machine while the timer is running and changes the system
260clock, the timer will nevertheless run (roughly) the same time. 293clock, the timer will nevertheless run (roughly) the same time.
261 294
262The C<timer_ns> variant doesn't start (activate) the newly created watcher. 295The C<timer_ns> variant doesn't start (activate) the newly created watcher.
263 296
268 301
269=item $w->again 302=item $w->again
270 303
271Similar to the C<start> method, but has special semantics for repeating timers: 304Similar to the C<start> method, but has special semantics for repeating timers:
272 305
306If the timer is active and non-repeating, it will be stopped.
307
273If the timer is active and repeating, reset the timeout to occur 308If the timer is active and repeating, reset the timeout to occur
274C<$repeat> seconds after now. 309C<$repeat> seconds after now.
275 310
276If the timer is active and non-repeating, it will be stopped.
277
278If the timer is in active and repeating, start it. 311If the timer is inactive and repeating, start it using the repeat value.
279 312
280Otherwise do nothing. 313Otherwise do nothing.
281 314
282This behaviour is useful when you have a timeout for some IO 315This 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 316operation. 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 317C<$repeat>, and then, in the read/write watcher, run the C<again> method
285on the timeout. 318on the timeout.
286 319
287 320
288=item $w = EV::periodic $at, $interval, $callback 321=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
289 322
290=item $w = EV::periodic_ns $at, $interval, $callback 323=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
291 324
292Similar to EV::timer, but the time is given as an absolute point in time 325Similar to EV::timer, but is not based on relative timeouts but on
293(C<$at>), plus an optional C<$interval>. 326absolute times. Apart from creating "simple" timers that trigger "at" the
327specified time, it can also be used for non-drifting absolute timers and
328more complex, cron-like, setups that are not adversely affected by time
329jumps (i.e. when the system clock is changed by explicit date -s or other
330means such as ntpd). It is also the most complex watcher type in EV.
294 331
295If the C<$interval> is zero, then the callback will be called at the time 332It has three distinct "modes":
296C<$at> if that is in the future, or as soon as possible if it is in the
297past. It will not automatically repeat.
298 333
299If the C<$interval> is nonzero, then the watcher will always be scheduled 334=over 4
300to time out at the next C<$at + N * $interval> time.
301 335
302This can be used to schedule a callback to run at very regular intervals, 336=item * absolute timer ($interval = $reschedule_cb = 0)
303as long as the processing time is less then the interval (otherwise 337
304obviously events will be skipped). 338This 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
340at January 1st 2011 then it will run when the system time reaches or
341surpasses this time.
342
343=item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0)
344
345In 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,
347regardless of any time jumps.
348
349This can be used to create timers that do not drift with respect to system
350time:
351
352 my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" };
353
354That doesn't mean there will always be 3600 seconds in between triggers,
355but only that the the clalback will be called when the system time shows a
356full hour (UTC).
305 357
306Another way to think about it (for the mathematically inclined) is that 358Another 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 359EV::periodic will try to run the callback in this mode at the next
308C<$time = $at (mod $interval)>, regardless of any time jumps. 360possible time where C<$time = $at (mod $interval)>, regardless of any time
361jumps.
309 362
310This periodic timer is based on "wallclock time", that is, if the clock 363=item * manual reschedule mode ($reschedule_cb = coderef)
311changes (C<ntp>, C<date -s> etc.), then the timer will nevertheless run at 364
312the specified time. This means it will never drift (it might jitter, but 365In this mode $interval and $at are both being ignored. Instead, each
313it will not drift). 366time the periodic watcher gets scheduled, the reschedule callback
367($reschedule_cb) will be called with the watcher as first, and the current
368time as second argument.
369
370I<This callback MUST NOT stop or destroy this or any other periodic
371watcher, ever>. If you need to stop it, return 1e30 and stop it
372afterwards.
373
374It must return the next time to trigger, based on the passed time value
375(that is, the lowest time value larger than to the second argument). It
376will usually be called just before the callback will be triggered, but
377might be called at other times, too.
378
379This can be used to create very complex timers, such as a timer that
380triggers on each midnight, local time (actually 24 hours after the last
381midnight, to keep the example simple. If you know a way to do it correctly
382in about the same space (without requiring elaborate modules), drop me a
383note :):
384
385 my $daily = EV::periodic 0, 0, sub {
386 my ($w, $now) = @_;
387
388 use Time::Local ();
389 my (undef, undef, undef, $d, $m, $y) = localtime $now;
390 86400 + Time::Local::timelocal 0, 0, 0, $d, $m, $y
391 }, sub {
392 print "it's midnight or likely shortly after, now\n";
393 };
394
395=back
314 396
315The C<periodic_ns> variant doesn't start (activate) the newly created watcher. 397The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
316 398
317=item $w->set ($at, $interval) 399=item $w->set ($at, $interval, $reschedule_cb)
318 400
319Reconfigures the watcher, see the constructor above for details. Can be at 401Reconfigures the watcher, see the constructor above for details. Can be at
320any time. 402any time.
403
404=item $w->again
405
406Simply stops and starts the watcher again.
321 407
322 408
323=item $w = EV::signal $signal, $callback 409=item $w = EV::signal $signal, $callback
324 410
325=item $w = EV::signal_ns $signal, $callback 411=item $w = EV::signal_ns $signal, $callback
356Call the callback when a status change for pid C<$pid> (or any pid 442Call the callback when a status change for pid C<$pid> (or any pid
357if C<$pid> is 0) has been received. More precisely: when the process 443if C<$pid> is 0) has been received. More precisely: when the process
358receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all 444receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all
359changed/zombie children and call the callback. 445changed/zombie children and call the callback.
360 446
361Unlike all other callbacks, this callback will be called with an 447You can access both status and pid by using the C<rstatus> and C<rpid>
362additional third argument which is the exit status. See the C<waitpid> 448methods on the watcher object.
363function for details.
364 449
365You can have as many pid watchers per pid as you want. 450You can have as many pid watchers per pid as you want.
366 451
367The C<child_ns> variant doesn't start (activate) the newly created watcher. 452The C<child_ns> variant doesn't start (activate) the newly created watcher.
368 453
374=item $current_pid = $w->pid 459=item $current_pid = $w->pid
375 460
376=item $old_pid = $w->pid ($new_pid) 461=item $old_pid = $w->pid ($new_pid)
377 462
378Returns the previously set process id and optionally set a new one. 463Returns the previously set process id and optionally set a new one.
464
465=item $exit_status = $w->rstatus
466
467Return the exit/wait status (as returned by waitpid, see the waitpid entry
468in perlfunc).
469
470=item $pid = $w->rpid
471
472Return the pid of the awaited child (useful when you have installed a
473watcher for all pids).
379 474
380 475
381=item $w = EV::idle $callback 476=item $w = EV::idle $callback
382 477
383=item $w = EV::idle_ns $callback 478=item $w = EV::idle_ns $callback
421 # do nothing unless active 516 # do nothing unless active
422 $dispatcher->{_event_queue_h} 517 $dispatcher->{_event_queue_h}
423 or return; 518 or return;
424 519
425 # make the dispatcher handle any outstanding stuff 520 # make the dispatcher handle any outstanding stuff
521 ... not shown
426 522
427 # create an IO watcher for each and every socket 523 # create an IO watcher for each and every socket
428 @snmp_watcher = ( 524 @snmp_watcher = (
429 (map { EV::io $_, EV::READ, sub { } } 525 (map { EV::io $_, EV::READ, sub { } }
430 keys %{ $dispatcher->{_descriptors} }), 526 keys %{ $dispatcher->{_descriptors} }),
527
528 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
529 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
530 0, sub { },
431 ); 531 );
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 }; 532 };
437 533
438The callbacks are irrelevant, the only purpose of those watchers is 534The callbacks are irrelevant (and are not even being called), the
439to wake up the process as soon as one of those events occurs (socket 535only 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 536one of those events occurs (socket readable, or timer timed out). The
441clean up: 537corresponding EV::check watcher will then clean up:
442 538
443 our $snmp_check = EV::check sub { 539 our $snmp_check = EV::check sub {
444 # destroy all watchers 540 # destroy all watchers
445 @snmp_watcher = (); 541 @snmp_watcher = ();
446 542
447 # make the dispatcher handle any new stuff 543 # make the dispatcher handle any new stuff
544 ... not shown
448 }; 545 };
449 546
450The callbacks of the created watchers will not be called as the watchers 547The callbacks of the created watchers will not be called as the watchers
451are destroyed before this cna happen (remember EV::check gets called 548are destroyed before this cna happen (remember EV::check gets called
452first). 549first).
455 552
456=back 553=back
457 554
458=head1 THREADS 555=head1 THREADS
459 556
460Threads are not supported by this in any way. Perl pseudo-threads is evil 557Threads are not supported by this module in any way. Perl pseudo-threads
461stuff and must die. 558is evil stuff and must die. As soon as Perl gains real threads I will work
559on thread support for it.
560
561=head1 FORK
562
563Most of the "improved" event delivering mechanisms of modern operating
564systems have quite a few problems with fork(2) (to put it bluntly: it is
565not supported and usually destructive). Libev makes it possible to work
566around this by having a function that recreates the kernel state after
567fork in the child.
568
569On non-win32 platforms, this module requires the pthread_atfork
570functionality to do this automatically for you. This function is quite
571buggy on most BSDs, though, so YMMV. The overhead for this is quite
572negligible, because everything the function currently does is set a flag
573that is checked only when the event loop gets used the next time, so when
574you do fork but not use EV, the overhead is minimal.
575
576On win32, there is no notion of fork so all this doesn't apply, of course.
462 577
463=cut 578=cut
464 579
465our $DIED = sub { 580our $DIED = sub {
466 warn "EV: error in callback (ignoring): $@"; 581 warn "EV: error in callback (ignoring): $@";
467}; 582};
468 583
469init; 584default_loop
470 585 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?';
471push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
472 586
4731; 5871;
474 588
475=head1 SEE ALSO 589=head1 SEE ALSO
476 590
477 L<EV::DNS>, L<EV::AnyEvent>. 591 L<EV::DNS>.
478 592
479=head1 AUTHOR 593=head1 AUTHOR
480 594
481 Marc Lehmann <schmorp@schmorp.de> 595 Marc Lehmann <schmorp@schmorp.de>
482 http://home.schmorp.de/ 596 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines