… | |
… | |
56 | This module provides an interface to libev |
56 | This module provides an interface to libev |
57 | (<http://software.schmorp.de/pkg/libev.html>). While the documentation |
57 | (<http://software.schmorp.de/pkg/libev.html>). While the documentation |
58 | below is comprehensive, one might also consult the documentation of |
58 | below is comprehensive, one might also consult the documentation of |
59 | libev itself (<http://cvs.schmorp.de/libev/ev.html>) for more subtle |
59 | libev itself (<http://cvs.schmorp.de/libev/ev.html>) for more subtle |
60 | details on watcher semantics or some discussion on the available |
60 | details on watcher semantics or some discussion on the available |
61 | backends, or how to force a specific backend with "LIBEV_FLAGS". |
61 | backends, or how to force a specific backend with "LIBEV_FLAGS", or just |
|
|
62 | about in any case because it has much more detailed information. |
|
|
63 | |
|
|
64 | EVENT LOOPS |
|
|
65 | EV supports multiple event loops: There is a single "default event loop" |
|
|
66 | that can handle everything including signals and child watchers, and any |
|
|
67 | number of "dynamic event loops" that can use different backends (with |
|
|
68 | various limitations), but no child and signal watchers. |
|
|
69 | |
|
|
70 | You do not have to do anything to create the default event loop: When |
|
|
71 | the module is loaded a suitable backend is selected on the premise of |
|
|
72 | selecting a working backend (which for example rules out kqueue on most |
|
|
73 | BSDs). Modules should, unless they have "special needs" always use the |
|
|
74 | default loop as this is fastest (perl-wise), best supported by other |
|
|
75 | modules (e.g. AnyEvent or Coro) and most portable event loop. |
|
|
76 | |
|
|
77 | For specific programs you cna create additional event loops dynamically. |
|
|
78 | |
|
|
79 | $loop = new EV::loop [$flags] |
|
|
80 | Create a new event loop as per the specified flags. Please refer to |
|
|
81 | the "ev_loop_new ()" function description in the libev documentation |
|
|
82 | (<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTI |
|
|
83 | ONS>) for more info. |
|
|
84 | |
|
|
85 | The loop will automatically be destroyed when it is no longer |
|
|
86 | referenced by any watcher and the loop object goes out of scope. |
|
|
87 | |
|
|
88 | Using "EV::FLAG_FORKCHECK" is recommended, as only the default event |
|
|
89 | loop is protected by this module. |
|
|
90 | |
|
|
91 | $loop->loop_fork |
|
|
92 | Must be called after a fork in the child, before entering or |
|
|
93 | continuing the event loop. An alternative is to use |
|
|
94 | "EV::FLAG_FORKCHECK" which calls this fucntion automatically, at |
|
|
95 | some performance loss (refer to the libev documentation). |
62 | |
96 | |
63 | BASIC INTERFACE |
97 | BASIC INTERFACE |
64 | $EV::DIED |
98 | $EV::DIED |
65 | Must contain a reference to a function that is called when a |
99 | Must contain a reference to a function that is called when a |
66 | callback throws an exception (with $@ containing thr error). The |
100 | callback throws an exception (with $@ containing the error). The |
67 | default prints an informative message and continues. |
101 | default prints an informative message and continues. |
68 | |
102 | |
69 | If this callback throws an exception it will be silently ignored. |
103 | If this callback throws an exception it will be silently ignored. |
70 | |
104 | |
71 | $time = EV::time |
105 | $time = EV::time |
72 | Returns the current time in (fractional) seconds since the epoch. |
106 | Returns the current time in (fractional) seconds since the epoch. |
73 | |
107 | |
74 | $time = EV::now |
108 | $time = EV::now |
|
|
109 | $time = $loop->now |
75 | Returns the time the last event loop iteration has been started. |
110 | Returns the time the last event loop iteration has been started. |
76 | This is the time that (relative) timers are based on, and refering |
111 | This is the time that (relative) timers are based on, and refering |
77 | to it is usually faster then calling EV::time. |
112 | to it is usually faster then calling EV::time. |
78 | |
113 | |
79 | $method = EV::method |
114 | $backend = EV::backend |
|
|
115 | $backend = $loop->backend |
80 | Returns an integer describing the backend used by libev |
116 | Returns an integer describing the backend used by libev |
81 | (EV::METHOD_SELECT or EV::METHOD_EPOLL). |
117 | (EV::METHOD_SELECT or EV::METHOD_EPOLL). |
82 | |
118 | |
83 | EV::loop [$flags] |
119 | EV::loop [$flags] |
|
|
120 | $loop->loop ([$flags]) |
84 | Begin checking for events and calling callbacks. It returns when a |
121 | Begin checking for events and calling callbacks. It returns when a |
85 | callback calls EV::unloop. |
122 | callback calls EV::unloop. |
86 | |
123 | |
87 | The $flags argument can be one of the following: |
124 | The $flags argument can be one of the following: |
88 | |
125 | |
89 | 0 as above |
126 | 0 as above |
90 | EV::LOOP_ONESHOT block at most once (wait, but do not loop) |
127 | EV::LOOP_ONESHOT block at most once (wait, but do not loop) |
91 | EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) |
128 | EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) |
92 | |
129 | |
93 | EV::unloop [$how] |
130 | EV::unloop [$how] |
|
|
131 | $loop->unloop ([$how]) |
94 | When called with no arguments or an argument of EV::UNLOOP_ONE, |
132 | When called with no arguments or an argument of EV::UNLOOP_ONE, |
95 | makes the innermost call to EV::loop return. |
133 | makes the innermost call to EV::loop return. |
96 | |
134 | |
97 | When called with an argument of EV::UNLOOP_ALL, all calls to |
135 | When called with an argument of EV::UNLOOP_ALL, all calls to |
98 | EV::loop will return as fast as possible. |
136 | EV::loop will return as fast as possible. |
99 | |
137 | |
|
|
138 | $count = EV::loop_count |
|
|
139 | $count = $loop->loop_count |
|
|
140 | Return the number of times the event loop has polled for new events. |
|
|
141 | Sometiems useful as a generation counter. |
|
|
142 | |
100 | EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
143 | EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
|
|
144 | $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) |
101 | This function rolls together an I/O and a timer watcher for a single |
145 | This function rolls together an I/O and a timer watcher for a single |
102 | one-shot event without the need for managing a watcher object. |
146 | one-shot event without the need for managing a watcher object. |
103 | |
147 | |
104 | If $fh_or_undef is a filehandle or file descriptor, then $events |
148 | If $fh_or_undef is a filehandle or file descriptor, then $events |
105 | must be a bitset containing either "EV::READ", "EV::WRITE" or |
149 | must be a bitset containing either "EV::READ", "EV::WRITE" or |
… | |
… | |
110 | If timeout is "undef" or negative, then there will be no timeout. |
154 | If timeout is "undef" or negative, then there will be no timeout. |
111 | Otherwise a EV::timer with this value will be started. |
155 | Otherwise a EV::timer with this value will be started. |
112 | |
156 | |
113 | When an error occurs or either the timeout or I/O watcher triggers, |
157 | When an error occurs or either the timeout or I/O watcher triggers, |
114 | then the callback will be called with the received event set (in |
158 | then the callback will be called with the received event set (in |
115 | general you can expect it to be a combination of "EV:ERROR", |
159 | general you can expect it to be a combination of "EV::ERROR", |
116 | "EV::READ", "EV::WRITE" and "EV::TIMEOUT"). |
160 | "EV::READ", "EV::WRITE" and "EV::TIMEOUT"). |
117 | |
161 | |
118 | EV::once doesn't return anything: the watchers stay active till |
162 | EV::once doesn't return anything: the watchers stay active till |
119 | either of them triggers, then they will be stopped and freed, and |
163 | either of them triggers, then they will be stopped and freed, and |
120 | the callback invoked. |
164 | the callback invoked. |
121 | |
165 | |
|
|
166 | EV::feed_fd_event ($fd, $revents) |
|
|
167 | $loop->feed_fd_event ($fd, $revents) |
|
|
168 | Feed an event on a file descriptor into EV. EV will react to this |
|
|
169 | call as if the readyness notifications specified by $revents (a |
|
|
170 | combination of "EV::READ" and "EV::WRITE") happened on the file |
|
|
171 | descriptor $fd. |
|
|
172 | |
|
|
173 | EV::feed_signal_event ($signal) |
|
|
174 | Feed a signal event into EV. EV will react to this call as if the |
|
|
175 | signal specified by $signal had occured. |
|
|
176 | |
122 | WATCHER OBJECTS |
177 | WATCHER OBJECTS |
123 | A watcher is an object that gets created to record your interest in some |
178 | A watcher is an object that gets created to record your interest in some |
124 | event. For instance, if you want to wait for STDIN to become readable, |
179 | event. For instance, if you want to wait for STDIN to become readable, |
125 | you would create an EV::io watcher for that: |
180 | you would create an EV::io watcher for that: |
126 | |
181 | |
127 | my $watcher = EV::io *STDIN, EV::READ, sub { |
182 | my $watcher = EV::io *STDIN, EV::READ, sub { |
128 | my ($watcher, $revents) = @_; |
183 | my ($watcher, $revents) = @_; |
129 | warn "yeah, STDIN should not be readable without blocking!\n" |
184 | warn "yeah, STDIN should now be readable without blocking!\n" |
130 | }; |
185 | }; |
131 | |
186 | |
132 | All watchers can be active (waiting for events) or inactive (paused). |
187 | All watchers can be active (waiting for events) or inactive (paused). |
133 | Only active watchers will have their callbacks invoked. All callbacks |
188 | Only active watchers will have their callbacks invoked. All callbacks |
134 | will be called with at least two arguments: the watcher and a bitmask of |
189 | will be called with at least two arguments: the watcher and a bitmask of |
135 | received events. |
190 | received events. |
136 | |
191 | |
137 | Each watcher type has its associated bit in revents, so you can use the |
192 | Each watcher type has its associated bit in revents, so you can use the |
138 | same callback for multiple watchers. The event mask is named after the |
193 | same callback for multiple watchers. The event mask is named after the |
139 | type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
194 | type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
140 | EV::periodic sets EV::PERIODIC and so on, with the exception of IO |
195 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O |
141 | events (which can set both EV::READ and EV::WRITE bits), and EV::timer |
196 | events (which can set both EV::READ and EV::WRITE bits), and EV::timer |
142 | (which uses EV::TIMEOUT). |
197 | (which uses EV::TIMEOUT). |
143 | |
198 | |
144 | In the rare case where one wants to create a watcher but not start it at |
199 | In the rare case where one wants to create a watcher but not start it at |
145 | the same time, each constructor has a variant with a trailing "_ns" in |
200 | the same time, each constructor has a variant with a trailing "_ns" in |
… | |
… | |
163 | stopped watchers). |
218 | stopped watchers). |
164 | |
219 | |
165 | $w->stop |
220 | $w->stop |
166 | Stop a watcher if it is active. Also clear any pending events |
221 | Stop a watcher if it is active. Also clear any pending events |
167 | (events that have been received but that didn't yet result in a |
222 | (events that have been received but that didn't yet result in a |
168 | callback invocation), regardless of wether the watcher was active or |
223 | callback invocation), regardless of whether the watcher was active |
169 | not. |
224 | or not. |
170 | |
225 | |
171 | $bool = $w->is_active |
226 | $bool = $w->is_active |
172 | Returns true if the watcher is active, false otherwise. |
227 | Returns true if the watcher is active, false otherwise. |
173 | |
228 | |
174 | $current_data = $w->data |
229 | $current_data = $w->data |
… | |
… | |
197 | The default priority of any newly-created watcher is 0. |
252 | The default priority of any newly-created watcher is 0. |
198 | |
253 | |
199 | Note that the priority semantics have not yet been fleshed out and |
254 | Note that the priority semantics have not yet been fleshed out and |
200 | are subject to almost certain change. |
255 | are subject to almost certain change. |
201 | |
256 | |
202 | $w->trigger ($revents) |
257 | $w->invoke ($revents) |
203 | Call the callback *now* with the given event mask. |
258 | Call the callback *now* with the given event mask. |
|
|
259 | |
|
|
260 | $w->feed_event ($revents) |
|
|
261 | Feed some events on this watcher into EV. EV will react to this call |
|
|
262 | as if the watcher had received the given $revents mask. |
|
|
263 | |
|
|
264 | $revents = $w->clear_pending |
|
|
265 | If the watcher is pending, this function clears its pending status |
|
|
266 | and returns its $revents bitset (as if its callback was invoked). If |
|
|
267 | the watcher isn't pending it does nothing and returns 0. |
204 | |
268 | |
205 | $previous_state = $w->keepalive ($bool) |
269 | $previous_state = $w->keepalive ($bool) |
206 | Normally, "EV::loop" will return when there are no active watchers |
270 | Normally, "EV::loop" will return when there are no active watchers |
207 | (which is a "deadlock" because no progress can be made anymore). |
271 | (which is a "deadlock" because no progress can be made anymore). |
208 | This is convinient because it allows you to start your watchers (and |
272 | This is convinient because it allows you to start your watchers (and |
209 | your jobs), call "EV::loop" once and when it returns you know that |
273 | your jobs), call "EV::loop" once and when it returns you know that |
210 | all your jobs are finished (or they forgot to register some watchers |
274 | all your jobs are finished (or they forgot to register some watchers |
211 | for their task :). |
275 | for their task :). |
212 | |
276 | |
213 | Sometimes, however, this gets in your way, for example when you the |
277 | Sometimes, however, this gets in your way, for example when the |
214 | module that calls "EV::loop" (usually the main program) is not the |
278 | module that calls "EV::loop" (usually the main program) is not the |
215 | same module as a long-living watcher (for example a DNS client |
279 | same module as a long-living watcher (for example a DNS client |
216 | module written by somebody else even). Then you might want any |
280 | module written by somebody else even). Then you might want any |
217 | outstanding requests to be handled, but you would not want to keep |
281 | outstanding requests to be handled, but you would not want to keep |
218 | "EV::loop" from returning just because you happen to have this |
282 | "EV::loop" from returning just because you happen to have this |
… | |
… | |
223 | returning. |
287 | returning. |
224 | |
288 | |
225 | The initial value for keepalive is true (enabled), and you cna |
289 | The initial value for keepalive is true (enabled), and you cna |
226 | change it any time. |
290 | change it any time. |
227 | |
291 | |
228 | Example: Register an IO watcher for some UDP socket but do not keep |
292 | Example: Register an I/O watcher for some UDP socket but do not keep |
229 | the event loop from running just because of that watcher. |
293 | the event loop from running just because of that watcher. |
230 | |
294 | |
231 | my $udp_socket = ... |
295 | my $udp_socket = ... |
232 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
296 | my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... }; |
233 | $udp_watcher->keepalive (0); |
297 | $1000udp_watcher->keepalive (0); |
234 | |
298 | |
|
|
299 | $loop = $w->loop |
|
|
300 | Return the loop that this watcher is attached to. |
|
|
301 | |
235 | WATCHER TYPES |
302 | WATCHER TYPES |
236 | Each of the following subsections describes a single watcher type. |
303 | Each of the following subsections describes a single watcher type. |
237 | |
304 | |
238 | IO WATCHERS - is this file descriptor readable or writable? |
305 | I/O WATCHERS - is this file descriptor readable or writable? |
239 | $w = EV::io $fileno_or_fh, $eventmask, $callback |
306 | $w = EV::io $fileno_or_fh, $eventmask, $callback |
240 | $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
307 | $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
|
|
308 | $w = $loop->io ($fileno_or_fh, $eventmask, $callback) |
|
|
309 | $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback) |
241 | As long as the returned watcher object is alive, call the $callback |
310 | As long as the returned watcher object is alive, call the $callback |
242 | when at least one of events specified in $eventmask occurs. |
311 | when at least one of events specified in $eventmask occurs. |
243 | |
312 | |
244 | The $eventmask can be one or more of these constants ORed together: |
313 | The $eventmask can be one or more of these constants ORed together: |
245 | |
314 | |
… | |
… | |
262 | Returns the previously set event mask and optionally set a new one. |
331 | Returns the previously set event mask and optionally set a new one. |
263 | |
332 | |
264 | TIMER WATCHERS - relative and optionally repeating timeouts |
333 | TIMER WATCHERS - relative and optionally repeating timeouts |
265 | $w = EV::timer $after, $repeat, $callback |
334 | $w = EV::timer $after, $repeat, $callback |
266 | $w = EV::timer_ns $after, $repeat, $callback |
335 | $w = EV::timer_ns $after, $repeat, $callback |
|
|
336 | $w = $loop->timer ($after, $repeat, $callback) |
|
|
337 | $w = $loop->timer_ns ($after, $repeat, $callback) |
267 | Calls the callback after $after seconds (which may be fractional). |
338 | Calls the callback after $after seconds (which may be fractional). |
268 | If $repeat is non-zero, the timer will be restarted (with the |
339 | If $repeat is non-zero, the timer will be restarted (with the |
269 | $repeat value as $after) after the callback returns. |
340 | $repeat value as $after) after the callback returns. |
270 | |
341 | |
271 | This means that the callback would be called roughly after $after |
342 | This means that the callback would be called roughly after $after |
… | |
… | |
307 | method on the timeout. |
378 | method on the timeout. |
308 | |
379 | |
309 | PERIODIC WATCHERS - to cron or not to cron? |
380 | PERIODIC WATCHERS - to cron or not to cron? |
310 | $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
381 | $w = EV::periodic $at, $interval, $reschedule_cb, $callback |
311 | $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
382 | $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback |
|
|
383 | $w = $loop->periodic ($at, $interval, $reschedule_cb, $callback) |
|
|
384 | $w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback) |
312 | Similar to EV::timer, but is not based on relative timeouts but on |
385 | Similar to EV::timer, but is not based on relative timeouts but on |
313 | absolute times. Apart from creating "simple" timers that trigger |
386 | absolute times. Apart from creating "simple" timers that trigger |
314 | "at" the specified time, it can also be used for non-drifting |
387 | "at" the specified time, it can also be used for non-drifting |
315 | absolute timers and more complex, cron-like, setups that are not |
388 | absolute timers and more complex, cron-like, setups that are not |
316 | adversely affected by time jumps (i.e. when the system clock is |
389 | adversely affected by time jumps (i.e. when the system clock is |
… | |
… | |
384 | be called at any time. |
457 | be called at any time. |
385 | |
458 | |
386 | $w->again |
459 | $w->again |
387 | Simply stops and starts the watcher again. |
460 | Simply stops and starts the watcher again. |
388 | |
461 | |
|
|
462 | $time = $w->at |
|
|
463 | Return the time that the watcher is expected to trigger next. |
|
|
464 | |
389 | SIGNAL WATCHERS - signal me when a signal gets signalled! |
465 | SIGNAL WATCHERS - signal me when a signal gets signalled! |
390 | $w = EV::signal $signal, $callback |
466 | $w = EV::signal $signal, $callback |
391 | $w = EV::signal_ns $signal, $callback |
467 | $w = EV::signal_ns $signal, $callback |
392 | Call the callback when $signal is received (the signal can be |
468 | Call the callback when $signal is received (the signal can be |
393 | specified by number or by name, just as with "kill" or %SIG). |
469 | specified by number or by name, just as with "kill" or %SIG). |
… | |
… | |
412 | optionally set a new one. |
488 | optionally set a new one. |
413 | |
489 | |
414 | CHILD WATCHERS - watch out for process status changes |
490 | CHILD WATCHERS - watch out for process status changes |
415 | $w = EV::child $pid, $callback |
491 | $w = EV::child $pid, $callback |
416 | $w = EV::child_ns $pid, $callback |
492 | $w = EV::child_ns $pid, $callback |
|
|
493 | $w = $loop->child ($pid, $callback) |
|
|
494 | $w = $loop->child_ns ($pid, $callback) |
417 | Call the callback when a status change for pid $pid (or any pid if |
495 | Call the callback when a status change for pid $pid (or any pid if |
418 | $pid is 0) has been received. More precisely: when the process |
496 | $pid is 0) has been received. More precisely: when the process |
419 | receives a "SIGCHLD", EV will fetch the outstanding exit/wait status |
497 | receives a "SIGCHLD", EV will fetch the outstanding exit/wait status |
420 | for all changed/zombie children and call the callback. |
498 | for all changed/zombie children and call the callback. |
421 | |
499 | |
… | |
… | |
451 | a watcher for all pids). |
529 | a watcher for all pids). |
452 | |
530 | |
453 | STAT WATCHERS - did the file attributes just change? |
531 | STAT WATCHERS - did the file attributes just change? |
454 | $w = EV::stat $path, $interval, $callback |
532 | $w = EV::stat $path, $interval, $callback |
455 | $w = EV::stat_ns $path, $interval, $callback |
533 | $w = EV::stat_ns $path, $interval, $callback |
|
|
534 | $w = $loop->stat ($path, $interval, $callback) |
|
|
535 | $w = $loop->stat_ns ($path, $interval, $callback) |
456 | Call the callback when a file status change has been detected on |
536 | Call the callback when a file status change has been detected on |
457 | $path. The $path does not need to exist, changing from "path exists" |
537 | $path. The $path does not need to exist, changing from "path exists" |
458 | to "path does not exist" is a status change like any other. |
538 | to "path does not exist" is a status change like any other. |
459 | |
539 | |
460 | The $interval is a recommended polling interval for systems where |
540 | The $interval is a recommended polling interval for systems where |
… | |
… | |
520 | Can be used to query the actual interval used. |
600 | Can be used to query the actual interval used. |
521 | |
601 | |
522 | IDLE WATCHERS - when you've got nothing better to do... |
602 | IDLE WATCHERS - when you've got nothing better to do... |
523 | $w = EV::idle $callback |
603 | $w = EV::idle $callback |
524 | $w = EV::idle_ns $callback |
604 | $w = EV::idle_ns $callback |
|
|
605 | $w = $loop->idle ($callback) |
|
|
606 | $w = $loop->idle_ns ($callback) |
525 | Call the callback when there are no pending io, timer/periodic, |
607 | Call the callback when there are no other pending watchers of the |
526 | signal or child events, i.e. when the process is idle. |
608 | same or higher priority (excluding check, prepare and other idle |
|
|
609 | watchers of the same or lower priority, of course). They are called |
|
|
610 | idle watchers because when the watcher is the highest priority |
|
|
611 | pending event in the process, the process is considered to be idle |
|
|
612 | at that priority. |
|
|
613 | |
|
|
614 | If you want a watcher that is only ever called when *no* other |
|
|
615 | events are outstanding you have to set the priority to "EV::MINPRI". |
527 | |
616 | |
528 | The process will not block as long as any idle watchers are active, |
617 | The process will not block as long as any idle watchers are active, |
529 | and they will be called repeatedly until stopped. |
618 | and they will be called repeatedly until stopped. |
|
|
619 | |
|
|
620 | For example, if you have idle watchers at priority 0 and 1, and an |
|
|
621 | I/O watcher at priority 0, then the idle watcher at priority 1 and |
|
|
622 | the I/O watcher will always run when ready. Only when the idle |
|
|
623 | watcher at priority 1 is stopped and the I/O watcher at priority 0 |
|
|
624 | is not pending with the 0-priority idle watcher be invoked. |
530 | |
625 | |
531 | The "idle_ns" variant doesn't start (activate) the newly created |
626 | The "idle_ns" variant doesn't start (activate) the newly created |
532 | watcher. |
627 | watcher. |
533 | |
628 | |
534 | PREPARE WATCHERS - customise your event loop! |
629 | PREPARE WATCHERS - customise your event loop! |
535 | $w = EV::prepare $callback |
630 | $w = EV::prepare $callback |
536 | $w = EV::prepare_ns $callback |
631 | $w = EV::prepare_ns $callback |
|
|
632 | $w = $loop->prepare ($callback) |
|
|
633 | $w = $loop->prepare_ns ($callback) |
537 | Call the callback just before the process would block. You can still |
634 | Call the callback just before the process would block. You can still |
538 | create/modify any watchers at this point. |
635 | create/modify any watchers at this point. |
539 | |
636 | |
540 | See the EV::check watcher, below, for explanations and an example. |
637 | See the EV::check watcher, below, for explanations and an example. |
541 | |
638 | |
… | |
… | |
543 | watcher. |
640 | watcher. |
544 | |
641 | |
545 | CHECK WATCHERS - customise your event loop even more! |
642 | CHECK WATCHERS - customise your event loop even more! |
546 | $w = EV::check $callback |
643 | $w = EV::check $callback |
547 | $w = EV::check_ns $callback |
644 | $w = EV::check_ns $callback |
|
|
645 | $w = $loop->check ($callback) |
|
|
646 | $w = $loop->check_ns ($callback) |
548 | Call the callback just after the process wakes up again (after it |
647 | Call the callback just after the process wakes up again (after it |
549 | has gathered events), but before any other callbacks have been |
648 | has gathered events), but before any other callbacks have been |
550 | invoked. |
649 | invoked. |
551 | |
650 | |
552 | This is used to integrate other event-based software into the EV |
651 | This is used to integrate other event-based software into the EV |
… | |
… | |
563 | or return; |
662 | or return; |
564 | |
663 | |
565 | # make the dispatcher handle any outstanding stuff |
664 | # make the dispatcher handle any outstanding stuff |
566 | ... not shown |
665 | ... not shown |
567 | |
666 | |
568 | # create an IO watcher for each and every socket |
667 | # create an I/O watcher for each and every socket |
569 | @snmp_watcher = ( |
668 | @snmp_watcher = ( |
570 | (map { EV::io $_, EV::READ, sub { } } |
669 | (map { EV::io $_, EV::READ, sub { } } |
571 | keys %{ $dispatcher->{_descriptors} }), |
670 | keys %{ $dispatcher->{_descriptors} }), |
572 | |
671 | |
573 | EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] |
672 | EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE] |
… | |
… | |
601 | is done before the event loop blocks next and before "check" watchers |
700 | is done before the event loop blocks next and before "check" watchers |
602 | are being called, and only in the child after the fork. |
701 | are being called, and only in the child after the fork. |
603 | |
702 | |
604 | $w = EV::fork $callback |
703 | $w = EV::fork $callback |
605 | $w = EV::fork_ns $callback |
704 | $w = EV::fork_ns $callback |
|
|
705 | $w = $loop->fork ($callback) |
|
|
706 | $w = $loop->fork_ns ($callback) |
606 | Call the callback before the event loop is resumed in the child |
707 | Call the callback before the event loop is resumed in the child |
607 | process after a fork. |
708 | process after a fork. |
608 | |
709 | |
609 | The "fork_ns" variant doesn't start (activate) the newly created |
710 | The "fork_ns" variant doesn't start (activate) the newly created |
610 | watcher. |
711 | watcher. |
|
|
712 | |
|
|
713 | PERL SIGNALS |
|
|
714 | While Perl signal handling (%SIG) is not affected by EV, the behaviour |
|
|
715 | with EV is as the same as any other C library: Perl-signals will only be |
|
|
716 | handled when Perl runs, which means your signal handler might be invoked |
|
|
717 | only the next time an event callback is invoked. |
|
|
718 | |
|
|
719 | The solution is to use EV signal watchers (see "EV::signal"), which will |
|
|
720 | ensure proper operations with regards to other event watchers. |
|
|
721 | |
|
|
722 | If you cannot do this for whatever reason, you can also force a watcher |
|
|
723 | to be called on every event loop iteration by installing a "EV::check" |
|
|
724 | watcher: |
|
|
725 | |
|
|
726 | my $async_check = EV::check sub { }; |
|
|
727 | |
|
|
728 | This ensures that perl gets into control for a short time to handle any |
|
|
729 | pending signals, and also ensures (slightly) slower overall operation. |
611 | |
730 | |
612 | THREADS |
731 | THREADS |
613 | Threads are not supported by this module in any way. Perl pseudo-threads |
732 | Threads are not supported by this module in any way. Perl pseudo-threads |
614 | is evil stuff and must die. As soon as Perl gains real threads I will |
733 | is evil stuff and must die. As soon as Perl gains real threads I will |
615 | work on thread support for it. |
734 | work on thread support for it. |
… | |
… | |
630 | |
749 | |
631 | On win32, there is no notion of fork so all this doesn't apply, of |
750 | On win32, there is no notion of fork so all this doesn't apply, of |
632 | course. |
751 | course. |
633 | |
752 | |
634 | SEE ALSO |
753 | SEE ALSO |
635 | EV::DNS. |
754 | EV::ADNS (asynchronous DNS), Glib::EV (makes Glib/Gtk2 use EV as event |
|
|
755 | loop), EV::Glib (embed Glib into EV), Coro::EV (efficient coroutines |
|
|
756 | with EV), Net::SNMP::EV (asynchronous SNMP). |
636 | |
757 | |
637 | AUTHOR |
758 | AUTHOR |
638 | Marc Lehmann <schmorp@schmorp.de> |
759 | Marc Lehmann <schmorp@schmorp.de> |
639 | http://home.schmorp.de/ |
760 | http://home.schmorp.de/ |
640 | |
761 | |