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

Comparing EV/README (file contents):
Revision 1.7 by root, Sat Nov 3 16:25:49 2007 UTC vs.
Revision 1.37 by root, Sat Oct 23 22:25:44 2010 UTC

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

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines