… | |
… | |
41 | my ($w, $revents) = @_; |
41 | my ($w, $revents) = @_; |
42 | my $status = $w->rstatus; |
42 | my $status = $w->rstatus; |
43 | }; |
43 | }; |
44 | |
44 | |
45 | # MAINLOOP |
45 | # MAINLOOP |
46 | EV::loop; # loop until EV::loop_done is called or all watchers stop |
46 | 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 |
47 | 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 |
48 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
49 | |
49 | |
50 | =head1 DESCRIPTION |
50 | =head1 DESCRIPTION |
51 | |
51 | |
… | |
… | |
57 | package EV; |
57 | package EV; |
58 | |
58 | |
59 | use strict; |
59 | use strict; |
60 | |
60 | |
61 | BEGIN { |
61 | BEGIN { |
62 | our $VERSION = '0.8'; |
62 | our $VERSION = '1.2'; |
63 | use XSLoader; |
63 | use XSLoader; |
64 | XSLoader::load "EV", $VERSION; |
64 | XSLoader::load "EV", $VERSION; |
65 | } |
65 | } |
66 | |
66 | |
67 | @EV::Io::ISA = |
67 | @EV::Io::ISA = |
… | |
… | |
93 | |
93 | |
94 | Returns the time the last event loop iteration has been started. This |
94 | Returns the time the last event loop iteration has been started. This |
95 | is the time that (relative) timers are based on, and refering to it is |
95 | is the time that (relative) timers are based on, and refering to it is |
96 | usually faster then calling EV::time. |
96 | usually faster then calling EV::time. |
97 | |
97 | |
98 | =item $method = EV::ev_method |
98 | =item $method = EV::method |
99 | |
99 | |
100 | Returns an integer describing the backend used by libev (EV::METHOD_SELECT |
100 | Returns an integer describing the backend used by libev (EV::METHOD_SELECT |
101 | or EV::METHOD_EPOLL). |
101 | or EV::METHOD_EPOLL). |
102 | |
102 | |
103 | =item EV::loop [$flags] |
103 | =item EV::loop [$flags] |
104 | |
104 | |
105 | Begin checking for events and calling callbacks. It returns when a |
105 | Begin checking for events and calling callbacks. It returns when a |
106 | callback calls EV::loop_done. |
106 | callback calls EV::unloop. |
107 | |
107 | |
108 | The $flags argument can be one of the following: |
108 | The $flags argument can be one of the following: |
109 | |
109 | |
110 | 0 as above |
110 | 0 as above |
111 | 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) |
112 | 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) |
113 | |
113 | |
114 | =item EV::loop_done [$how] |
114 | =item EV::unloop [$how] |
115 | |
115 | |
116 | When called with no arguments or an argument of 1, makes the innermost |
116 | When called with no arguments or an argument of EV::UNLOOP_ONE, makes the |
117 | call to EV::loop return. |
117 | innermost call to EV::loop return. |
118 | |
118 | |
119 | When called with an agrument of 2, all calls to EV::loop will return as |
119 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
120 | fast as possible. |
120 | fast as possible. |
|
|
121 | |
|
|
122 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($events) |
|
|
123 | |
|
|
124 | This function rolls together an I/O and a timer watcher for a single |
|
|
125 | one-shot event without the need for managing a watcher object. |
|
|
126 | |
|
|
127 | If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events> |
|
|
128 | must 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 |
|
|
130 | you do not want to wait for some I/O event, specify C<undef> for |
|
|
131 | C<$fh_or_undef> and C<0> for C<$events>). |
|
|
132 | |
|
|
133 | If timeout is C<undef> or negative, then there will be no |
|
|
134 | timeout. Otherwise a EV::timer with this value will be started. |
|
|
135 | |
|
|
136 | When an error occurs or either the timeout or I/O watcher triggers, then |
|
|
137 | the callback will be called with the received event set (in general |
|
|
138 | you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>, |
|
|
139 | C<EV::WRITE> and C<EV::TIMEOUT>). |
|
|
140 | |
|
|
141 | EV::once doesn't return anything: the watchers stay active till either |
|
|
142 | of them triggers, then they will be stopped and freed, and the callback |
|
|
143 | invoked. |
121 | |
144 | |
122 | =back |
145 | =back |
123 | |
146 | |
124 | =head2 WATCHER |
147 | =head2 WATCHER |
125 | |
148 | |
… | |
… | |
258 | Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, |
281 | Calls the callback after C<$after> seconds. If C<$repeat> is non-zero, |
259 | the timer will be restarted (with the $repeat value as $after) after the |
282 | the timer will be restarted (with the $repeat value as $after) after the |
260 | callback returns. |
283 | callback returns. |
261 | |
284 | |
262 | This means that the callback would be called roughly after C<$after> |
285 | This means that the callback would be called roughly after C<$after> |
263 | seconds, and then every C<$repeat> seconds. "Roughly" because the time of |
286 | seconds, and then every C<$repeat> seconds. The timer does his best not |
264 | callback processing is not taken into account, so the timer will slowly |
287 | to drift, but it will not invoke the timer more often then once per event |
265 | drift. If that isn't acceptable, look at EV::periodic. |
288 | loop iteration, and might drift in other cases. If that isn't acceptable, |
|
|
289 | look at EV::periodic, which can provide long-term stable timers. |
266 | |
290 | |
267 | The timer is based on a monotonic clock, that is if somebody is sitting |
291 | The timer is based on a monotonic clock, that is, if somebody is sitting |
268 | in front of the machine while the timer is running and changes the system |
292 | in front of the machine while the timer is running and changes the system |
269 | clock, the timer will nevertheless run (roughly) the same time. |
293 | clock, the timer will nevertheless run (roughly) the same time. |
270 | |
294 | |
271 | The C<timer_ns> variant doesn't start (activate) the newly created watcher. |
295 | The C<timer_ns> variant doesn't start (activate) the newly created watcher. |
272 | |
296 | |
… | |
… | |
277 | |
301 | |
278 | =item $w->again |
302 | =item $w->again |
279 | |
303 | |
280 | Similar to the C<start> method, but has special semantics for repeating timers: |
304 | Similar to the C<start> method, but has special semantics for repeating timers: |
281 | |
305 | |
|
|
306 | If the timer is active and non-repeating, it will be stopped. |
|
|
307 | |
282 | If the timer is active and repeating, reset the timeout to occur |
308 | If the timer is active and repeating, reset the timeout to occur |
283 | C<$repeat> seconds after now. |
309 | C<$repeat> seconds after now. |
284 | |
310 | |
285 | If the timer is active and non-repeating, it will be stopped. |
|
|
286 | |
|
|
287 | If the timer is in active and repeating, start it. |
311 | If the timer is inactive and repeating, start it using the repeat value. |
288 | |
312 | |
289 | Otherwise do nothing. |
313 | Otherwise do nothing. |
290 | |
314 | |
291 | This behaviour is useful when you have a timeout for some IO |
315 | This behaviour is useful when you have a timeout for some IO |
292 | operation. You create a timer object with the same value for C<$after> and |
316 | operation. You create a timer object with the same value for C<$after> and |
… | |
… | |
492 | # do nothing unless active |
516 | # do nothing unless active |
493 | $dispatcher->{_event_queue_h} |
517 | $dispatcher->{_event_queue_h} |
494 | or return; |
518 | or return; |
495 | |
519 | |
496 | # make the dispatcher handle any outstanding stuff |
520 | # make the dispatcher handle any outstanding stuff |
|
|
521 | ... not shown |
497 | |
522 | |
498 | # create an IO watcher for each and every socket |
523 | # create an IO watcher for each and every socket |
499 | @snmp_watcher = ( |
524 | @snmp_watcher = ( |
500 | (map { EV::io $_, EV::READ, sub { } } |
525 | (map { EV::io $_, EV::READ, sub { } } |
501 | 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 { }, |
502 | ); |
531 | ); |
503 | |
|
|
504 | # if there are any timeouts, also create a timer |
|
|
505 | push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { } |
|
|
506 | if $event->[Net::SNMP::Dispatcher::_ACTIVE]; |
|
|
507 | }; |
532 | }; |
508 | |
533 | |
509 | The callbacks are irrelevant, the only purpose of those watchers is |
534 | The callbacks are irrelevant (and are not even being called), the |
510 | to wake up the process as soon as one of those events occurs (socket |
535 | only purpose of those watchers is to wake up the process as soon as |
511 | readable, or timer timed out). The corresponding EV::check watcher will then |
536 | one of those events occurs (socket readable, or timer timed out). The |
512 | clean up: |
537 | corresponding EV::check watcher will then clean up: |
513 | |
538 | |
514 | our $snmp_check = EV::check sub { |
539 | our $snmp_check = EV::check sub { |
515 | # destroy all watchers |
540 | # destroy all watchers |
516 | @snmp_watcher = (); |
541 | @snmp_watcher = (); |
517 | |
542 | |
518 | # make the dispatcher handle any new stuff |
543 | # make the dispatcher handle any new stuff |
|
|
544 | ... not shown |
519 | }; |
545 | }; |
520 | |
546 | |
521 | The callbacks of the created watchers will not be called as the watchers |
547 | The callbacks of the created watchers will not be called as the watchers |
522 | are destroyed before this cna happen (remember EV::check gets called |
548 | are destroyed before this cna happen (remember EV::check gets called |
523 | first). |
549 | first). |
… | |
… | |
526 | |
552 | |
527 | =back |
553 | =back |
528 | |
554 | |
529 | =head1 THREADS |
555 | =head1 THREADS |
530 | |
556 | |
531 | Threads are not supported by this in any way. Perl pseudo-threads is evil |
557 | Threads are not supported by this module in any way. Perl pseudo-threads |
532 | stuff and must die. |
558 | is evil stuff and must die. As soon as Perl gains real threads I will work |
|
|
559 | on thread support for it. |
|
|
560 | |
|
|
561 | =head1 FORK |
|
|
562 | |
|
|
563 | Most of the "improved" event delivering mechanisms of modern operating |
|
|
564 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
|
|
565 | not supported and usually destructive). Libev makes it possible to work |
|
|
566 | around this by having a function that recreates the kernel state after |
|
|
567 | fork in the child. |
|
|
568 | |
|
|
569 | On non-win32 platforms, this module requires the pthread_atfork |
|
|
570 | functionality to do this automatically for you. This function is quite |
|
|
571 | buggy on most BSDs, though, so YMMV. The overhead for this is quite |
|
|
572 | negligible, because everything the function currently does is set a flag |
|
|
573 | that is checked only when the event loop gets used the next time, so when |
|
|
574 | you do fork but not use EV, the overhead is minimal. |
|
|
575 | |
|
|
576 | On win32, there is no notion of fork so all this doesn't apply, of course. |
533 | |
577 | |
534 | =cut |
578 | =cut |
535 | |
579 | |
536 | our $DIED = sub { |
580 | our $DIED = sub { |
537 | warn "EV: error in callback (ignoring): $@"; |
581 | warn "EV: error in callback (ignoring): $@"; |
… | |
… | |
542 | |
586 | |
543 | 1; |
587 | 1; |
544 | |
588 | |
545 | =head1 SEE ALSO |
589 | =head1 SEE ALSO |
546 | |
590 | |
547 | L<EV::DNS>, L<EV::AnyEvent>. |
591 | L<EV::DNS>. |
548 | |
592 | |
549 | =head1 AUTHOR |
593 | =head1 AUTHOR |
550 | |
594 | |
551 | Marc Lehmann <schmorp@schmorp.de> |
595 | Marc Lehmann <schmorp@schmorp.de> |
552 | http://home.schmorp.de/ |
596 | http://home.schmorp.de/ |