… | |
… | |
124 | |
124 | |
125 | It supports the following flags: |
125 | It supports the following flags: |
126 | |
126 | |
127 | =over 4 |
127 | =over 4 |
128 | |
128 | |
129 | =item EVFLAG_AUTO |
129 | =item C<EVFLAG_AUTO> |
130 | |
130 | |
131 | The default flags value. Use this if you have no clue (it's the right |
131 | The default flags value. Use this if you have no clue (it's the right |
132 | thing, believe me). |
132 | thing, believe me). |
133 | |
133 | |
134 | =item EVFLAG_NOENV |
134 | =item C<EVFLAG_NOENV> |
135 | |
135 | |
136 | If this flag bit is ored into the flag value (or the program runs setuid |
136 | If this flag bit is ored into the flag value (or the program runs setuid |
137 | or setgid) then libev will I<not> look at the environment variable |
137 | or setgid) then libev will I<not> look at the environment variable |
138 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
138 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
139 | override the flags completely if it is found in the environment. This is |
139 | override the flags completely if it is found in the environment. This is |
140 | useful to try out specific backends to test their performance, or to work |
140 | useful to try out specific backends to test their performance, or to work |
141 | around bugs. |
141 | around bugs. |
142 | |
142 | |
143 | =item EVMETHOD_SELECT (portable select backend) |
143 | =item C<EVMETHOD_SELECT> (portable select backend) |
144 | |
144 | |
145 | =item EVMETHOD_POLL (poll backend, available everywhere except on windows) |
145 | =item C<EVMETHOD_POLL> (poll backend, available everywhere except on windows) |
146 | |
146 | |
147 | =item EVMETHOD_EPOLL (linux only) |
147 | =item C<EVMETHOD_EPOLL> (linux only) |
148 | |
148 | |
149 | =item EVMETHOD_KQUEUE (some bsds only) |
149 | =item C<EVMETHOD_KQUEUE> (some bsds only) |
150 | |
150 | |
151 | =item EVMETHOD_DEVPOLL (solaris 8 only) |
151 | =item C<EVMETHOD_DEVPOLL> (solaris 8 only) |
152 | |
152 | |
153 | =item EVMETHOD_PORT (solaris 10 only) |
153 | =item C<EVMETHOD_PORT> (solaris 10 only) |
154 | |
154 | |
155 | If one or more of these are ored into the flags value, then only these |
155 | If one or more of these are ored into the flags value, then only these |
156 | backends will be tried (in the reverse order as given here). If one are |
156 | backends will be tried (in the reverse order as given here). If one are |
157 | specified, any backend will do. |
157 | specified, any backend will do. |
158 | |
158 | |
… | |
… | |
260 | |
260 | |
261 | =head1 ANATOMY OF A WATCHER |
261 | =head1 ANATOMY OF A WATCHER |
262 | |
262 | |
263 | A watcher is a structure that you create and register to record your |
263 | A watcher is a structure that you create and register to record your |
264 | interest in some event. For instance, if you want to wait for STDIN to |
264 | interest in some event. For instance, if you want to wait for STDIN to |
265 | become readable, you would create an ev_io watcher for that: |
265 | become readable, you would create an C<ev_io> watcher for that: |
266 | |
266 | |
267 | static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
267 | static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
268 | { |
268 | { |
269 | ev_io_stop (w); |
269 | ev_io_stop (w); |
270 | ev_unloop (loop, EVUNLOOP_ALL); |
270 | ev_unloop (loop, EVUNLOOP_ALL); |
… | |
… | |
299 | |
299 | |
300 | As long as your watcher is active (has been started but not stopped) you |
300 | As long as your watcher is active (has been started but not stopped) you |
301 | must not touch the values stored in it. Most specifically you must never |
301 | must not touch the values stored in it. Most specifically you must never |
302 | reinitialise it or call its set method. |
302 | reinitialise it or call its set method. |
303 | |
303 | |
304 | You cna check whether an event is active by calling the C<ev_is_active |
304 | You can check whether an event is active by calling the C<ev_is_active |
305 | (watcher *)> macro. To see whether an event is outstanding (but the |
305 | (watcher *)> macro. To see whether an event is outstanding (but the |
306 | callback for it has not been called yet) you cna use the C<ev_is_pending |
306 | callback for it has not been called yet) you can use the C<ev_is_pending |
307 | (watcher *)> macro. |
307 | (watcher *)> macro. |
308 | |
308 | |
309 | Each and every callback receives the event loop pointer as first, the |
309 | Each and every callback receives the event loop pointer as first, the |
310 | registered watcher structure as second, and a bitset of received events as |
310 | registered watcher structure as second, and a bitset of received events as |
311 | third argument. |
311 | third argument. |
312 | |
312 | |
313 | The rceeived events usually include a single bit per event type received |
313 | The received events usually include a single bit per event type received |
314 | (you can receive multiple events at the same time). The possible bit masks |
314 | (you can receive multiple events at the same time). The possible bit masks |
315 | are: |
315 | are: |
316 | |
316 | |
317 | =over 4 |
317 | =over 4 |
318 | |
318 | |
319 | =item EV_READ |
319 | =item C<EV_READ> |
320 | |
320 | |
321 | =item EV_WRITE |
321 | =item C<EV_WRITE> |
322 | |
322 | |
323 | The file descriptor in the ev_io watcher has become readable and/or |
323 | The file descriptor in the C<ev_io> watcher has become readable and/or |
324 | writable. |
324 | writable. |
325 | |
325 | |
326 | =item EV_TIMEOUT |
326 | =item C<EV_TIMEOUT> |
327 | |
327 | |
328 | The ev_timer watcher has timed out. |
328 | The C<ev_timer> watcher has timed out. |
329 | |
329 | |
330 | =item EV_PERIODIC |
330 | =item C<EV_PERIODIC> |
331 | |
331 | |
332 | The ev_periodic watcher has timed out. |
332 | The C<ev_periodic> watcher has timed out. |
333 | |
333 | |
334 | =item EV_SIGNAL |
334 | =item C<EV_SIGNAL> |
335 | |
335 | |
336 | The signal specified in the ev_signal watcher has been received by a thread. |
336 | The signal specified in the C<ev_signal> watcher has been received by a thread. |
337 | |
337 | |
338 | =item EV_CHILD |
338 | =item C<EV_CHILD> |
339 | |
339 | |
340 | The pid specified in the ev_child watcher has received a status change. |
340 | The pid specified in the C<ev_child> watcher has received a status change. |
341 | |
341 | |
342 | =item EV_IDLE |
342 | =item C<EV_IDLE> |
343 | |
343 | |
344 | The ev_idle watcher has determined that you have nothing better to do. |
344 | The C<ev_idle> watcher has determined that you have nothing better to do. |
345 | |
345 | |
346 | =item EV_PREPARE |
346 | =item C<EV_PREPARE> |
347 | |
347 | |
348 | =item EV_CHECK |
348 | =item C<EV_CHECK> |
349 | |
349 | |
350 | All ev_prepare watchers are invoked just I<before> C<ev_loop> starts |
350 | All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts |
351 | to gather new events, and all ev_check watchers are invoked just after |
351 | to gather new events, and all C<ev_check> watchers are invoked just after |
352 | C<ev_loop> has gathered them, but before it invokes any callbacks for any |
352 | C<ev_loop> has gathered them, but before it invokes any callbacks for any |
353 | received events. Callbacks of both watcher types can start and stop as |
353 | received events. Callbacks of both watcher types can start and stop as |
354 | many watchers as they want, and all of them will be taken into account |
354 | many watchers as they want, and all of them will be taken into account |
355 | (for example, a ev_prepare watcher might start an idle watcher to keep |
355 | (for example, a C<ev_prepare> watcher might start an idle watcher to keep |
356 | C<ev_loop> from blocking). |
356 | C<ev_loop> from blocking). |
357 | |
357 | |
358 | =item EV_ERROR |
358 | =item C<EV_ERROR> |
359 | |
359 | |
360 | An unspecified error has occured, the watcher has been stopped. This might |
360 | An unspecified error has occured, the watcher has been stopped. This might |
361 | happen because the watcher could not be properly started because libev |
361 | happen because the watcher could not be properly started because libev |
362 | ran out of memory, a file descriptor was found to be closed or any other |
362 | ran out of memory, a file descriptor was found to be closed or any other |
363 | problem. You best act on it by reporting the problem and somehow coping |
363 | problem. You best act on it by reporting the problem and somehow coping |
… | |
… | |
372 | =back |
372 | =back |
373 | |
373 | |
374 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
374 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
375 | |
375 | |
376 | Each watcher has, by default, a member C<void *data> that you can change |
376 | Each watcher has, by default, a member C<void *data> that you can change |
377 | and read at any time, libev will completely ignore it. This cna be used |
377 | and read at any time, libev will completely ignore it. This can be used |
378 | to associate arbitrary data with your watcher. If you need more data and |
378 | to associate arbitrary data with your watcher. If you need more data and |
379 | don't want to allocate memory and store a pointer to it in that data |
379 | don't want to allocate memory and store a pointer to it in that data |
380 | member, you can also "subclass" the watcher type and provide your own |
380 | member, you can also "subclass" the watcher type and provide your own |
381 | data: |
381 | data: |
382 | |
382 | |
… | |
… | |
404 | =head1 WATCHER TYPES |
404 | =head1 WATCHER TYPES |
405 | |
405 | |
406 | This section describes each watcher in detail, but will not repeat |
406 | This section describes each watcher in detail, but will not repeat |
407 | information given in the last section. |
407 | information given in the last section. |
408 | |
408 | |
409 | =head2 struct ev_io - is my file descriptor readable or writable |
409 | =head2 C<ev_io> - is this file descriptor readable or writable |
410 | |
410 | |
411 | I/O watchers check whether a file descriptor is readable or writable |
411 | I/O watchers check whether a file descriptor is readable or writable |
412 | in each iteration of the event loop (This behaviour is called |
412 | in each iteration of the event loop (This behaviour is called |
413 | level-triggering because you keep receiving events as long as the |
413 | level-triggering because you keep receiving events as long as the |
414 | condition persists. Remember you cna stop the watcher if you don't want to |
414 | condition persists. Remember you can stop the watcher if you don't want to |
415 | act on the event and neither want to receive future events). |
415 | act on the event and neither want to receive future events). |
416 | |
416 | |
417 | In general you can register as many read and/or write event watchers oer |
417 | In general you can register as many read and/or write event watchers oer |
418 | fd as you want (as long as you don't confuse yourself). Setting all file |
418 | fd as you want (as long as you don't confuse yourself). Setting all file |
419 | descriptors to non-blocking mode is also usually a good idea (but not |
419 | descriptors to non-blocking mode is also usually a good idea (but not |
… | |
… | |
432 | |
432 | |
433 | =item ev_io_init (ev_io *, callback, int fd, int events) |
433 | =item ev_io_init (ev_io *, callback, int fd, int events) |
434 | |
434 | |
435 | =item ev_io_set (ev_io *, int fd, int events) |
435 | =item ev_io_set (ev_io *, int fd, int events) |
436 | |
436 | |
437 | Configures an ev_io watcher. The fd is the file descriptor to rceeive |
437 | Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive |
438 | events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ | |
438 | events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ | |
439 | EV_WRITE> to receive the given events. |
439 | EV_WRITE> to receive the given events. |
440 | |
440 | |
441 | =back |
441 | =back |
442 | |
442 | |
443 | =head2 struct ev_timer - relative and optionally recurring timeouts |
443 | =head2 C<ev_timer> - relative and optionally recurring timeouts |
444 | |
444 | |
445 | Timer watchers are simple relative timers that generate an event after a |
445 | Timer watchers are simple relative timers that generate an event after a |
446 | given time, and optionally repeating in regular intervals after that. |
446 | given time, and optionally repeating in regular intervals after that. |
447 | |
447 | |
448 | The timers are based on real time, that is, if you register an event that |
448 | The timers are based on real time, that is, if you register an event that |
… | |
… | |
488 | |
488 | |
489 | This sounds a bit complicated, but here is a useful and typical |
489 | This sounds a bit complicated, but here is a useful and typical |
490 | example: Imagine you have a tcp connection and you want a so-called idle |
490 | example: Imagine you have a tcp connection and you want a so-called idle |
491 | timeout, that is, you want to be called when there have been, say, 60 |
491 | timeout, that is, you want to be called when there have been, say, 60 |
492 | seconds of inactivity on the socket. The easiest way to do this is to |
492 | seconds of inactivity on the socket. The easiest way to do this is to |
493 | configure an ev_timer with after=repeat=60 and calling ev_timer_again each |
493 | configure an C<ev_timer> with after=repeat=60 and calling ev_timer_again each |
494 | time you successfully read or write some data. If you go into an idle |
494 | time you successfully read or write some data. If you go into an idle |
495 | state where you do not expect data to travel on the socket, you can stop |
495 | state where you do not expect data to travel on the socket, you can stop |
496 | the timer, and again will automatically restart it if need be. |
496 | the timer, and again will automatically restart it if need be. |
497 | |
497 | |
498 | =back |
498 | =back |
499 | |
499 | |
500 | =head2 ev_periodic - to cron or not to cron it |
500 | =head2 C<ev_periodic> - to cron or not to cron |
501 | |
501 | |
502 | Periodic watchers are also timers of a kind, but they are very versatile |
502 | Periodic watchers are also timers of a kind, but they are very versatile |
503 | (and unfortunately a bit complex). |
503 | (and unfortunately a bit complex). |
504 | |
504 | |
505 | Unlike ev_timer's, they are not based on real time (or relative time) |
505 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
506 | but on wallclock time (absolute time). You can tell a periodic watcher |
506 | but on wallclock time (absolute time). You can tell a periodic watcher |
507 | to trigger "at" some specific point in time. For example, if you tell a |
507 | to trigger "at" some specific point in time. For example, if you tell a |
508 | periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () |
508 | periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () |
509 | + 10.>) and then reset your system clock to the last year, then it will |
509 | + 10.>) and then reset your system clock to the last year, then it will |
510 | take a year to trigger the event (unlike an ev_timer, which would trigger |
510 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
511 | roughly 10 seconds later and of course not if you reset your system time |
511 | roughly 10 seconds later and of course not if you reset your system time |
512 | again). |
512 | again). |
513 | |
513 | |
514 | They can also be used to implement vastly more complex timers, such as |
514 | They can also be used to implement vastly more complex timers, such as |
515 | triggering an event on eahc midnight, local time. |
515 | triggering an event on eahc midnight, local time. |
… | |
… | |
544 | |
544 | |
545 | ev_periodic_set (&periodic, 0., 3600., 0); |
545 | ev_periodic_set (&periodic, 0., 3600., 0); |
546 | |
546 | |
547 | This doesn't mean there will always be 3600 seconds in between triggers, |
547 | This doesn't mean there will always be 3600 seconds in between triggers, |
548 | but only that the the callback will be called when the system time shows a |
548 | but only that the the callback will be called when the system time shows a |
549 | full hour (UTC), or more correct, when the system time is evenly divisible |
549 | full hour (UTC), or more correctly, when the system time is evenly divisible |
550 | by 3600. |
550 | by 3600. |
551 | |
551 | |
552 | Another way to think about it (for the mathematically inclined) is that |
552 | Another way to think about it (for the mathematically inclined) is that |
553 | ev_periodic will try to run the callback in this mode at the next possible |
553 | C<ev_periodic> will try to run the callback in this mode at the next possible |
554 | time where C<time = at (mod interval)>, regardless of any time jumps. |
554 | time where C<time = at (mod interval)>, regardless of any time jumps. |
555 | |
555 | |
556 | =item * manual reschedule mode (reschedule_cb = callback) |
556 | =item * manual reschedule mode (reschedule_cb = callback) |
557 | |
557 | |
558 | In this mode the values for C<interval> and C<at> are both being |
558 | In this mode the values for C<interval> and C<at> are both being |
559 | ignored. Instead, each time the periodic watcher gets scheduled, the |
559 | ignored. Instead, each time the periodic watcher gets scheduled, the |
560 | reschedule callback will be called with the watcher as first, and the |
560 | reschedule callback will be called with the watcher as first, and the |
561 | current time as second argument. |
561 | current time as second argument. |
562 | |
562 | |
563 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
563 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
564 | periodic watcher, ever, or make any event loop modificstions>. If you need |
564 | periodic watcher, ever, or make any event loop modifications>. If you need |
565 | to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards. |
565 | to stop it, return C<now + 1e30> (or so, fudge fudge) and stop it afterwards. |
566 | |
566 | |
|
|
567 | Also, I<< this callback must always return a time that is later than the |
|
|
568 | passed C<now> value >>. Not even C<now> itself will be ok. |
|
|
569 | |
567 | Its prototype is c<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
570 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
568 | ev_tstamp now)>, e.g.: |
571 | ev_tstamp now)>, e.g.: |
569 | |
572 | |
570 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
573 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
571 | { |
574 | { |
572 | return now + 60.; |
575 | return now + 60.; |
… | |
… | |
591 | a different time than the last time it was called (e.g. in a crond like |
594 | a different time than the last time it was called (e.g. in a crond like |
592 | program when the crontabs have changed). |
595 | program when the crontabs have changed). |
593 | |
596 | |
594 | =back |
597 | =back |
595 | |
598 | |
596 | =head2 ev_signal - signal me when a signal gets signalled |
599 | =head2 C<ev_signal> - signal me when a signal gets signalled |
597 | |
600 | |
598 | Signal watchers will trigger an event when the process receives a specific |
601 | Signal watchers will trigger an event when the process receives a specific |
599 | signal one or more times. Even though signals are very asynchronous, libev |
602 | signal one or more times. Even though signals are very asynchronous, libev |
600 | will try it's best to deliver signals synchronously, i.e. as part of the |
603 | will try it's best to deliver signals synchronously, i.e. as part of the |
601 | normal event processing, like any other event. |
604 | normal event processing, like any other event. |
602 | |
605 | |
603 | You cna configure as many watchers as you like per signal. Only when the |
606 | You can configure as many watchers as you like per signal. Only when the |
604 | first watcher gets started will libev actually register a signal watcher |
607 | first watcher gets started will libev actually register a signal watcher |
605 | with the kernel (thus it coexists with your own signal handlers as long |
608 | with the kernel (thus it coexists with your own signal handlers as long |
606 | as you don't register any with libev). Similarly, when the last signal |
609 | as you don't register any with libev). Similarly, when the last signal |
607 | watcher for a signal is stopped libev will reset the signal handler to |
610 | watcher for a signal is stopped libev will reset the signal handler to |
608 | SIG_DFL (regardless of what it was set to before). |
611 | SIG_DFL (regardless of what it was set to before). |
… | |
… | |
616 | Configures the watcher to trigger on the given signal number (usually one |
619 | Configures the watcher to trigger on the given signal number (usually one |
617 | of the C<SIGxxx> constants). |
620 | of the C<SIGxxx> constants). |
618 | |
621 | |
619 | =back |
622 | =back |
620 | |
623 | |
621 | =head2 ev_child - wait for pid status changes |
624 | =head2 C<ev_child> - wait for pid status changes |
622 | |
625 | |
623 | Child watchers trigger when your process receives a SIGCHLD in response to |
626 | Child watchers trigger when your process receives a SIGCHLD in response to |
624 | some child status changes (most typically when a child of yours dies). |
627 | some child status changes (most typically when a child of yours dies). |
625 | |
628 | |
626 | =over 4 |
629 | =over 4 |
… | |
… | |
630 | =item ev_child_set (ev_child *, int pid) |
633 | =item ev_child_set (ev_child *, int pid) |
631 | |
634 | |
632 | Configures the watcher to wait for status changes of process C<pid> (or |
635 | Configures the watcher to wait for status changes of process C<pid> (or |
633 | I<any> process if C<pid> is specified as C<0>). The callback can look |
636 | I<any> process if C<pid> is specified as C<0>). The callback can look |
634 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
637 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
635 | the status word (use the macros from C<sys/wait.h>). The C<rpid> member |
638 | the status word (use the macros from C<sys/wait.h> and see your systems |
636 | contains the pid of the process causing the status change. |
639 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
|
|
640 | process causing the status change. |
637 | |
641 | |
638 | =back |
642 | =back |
639 | |
643 | |
640 | =head2 ev_idle - when you've got nothing better to do |
644 | =head2 C<ev_idle> - when you've got nothing better to do |
641 | |
645 | |
642 | Idle watchers trigger events when there are no other I/O or timer (or |
646 | Idle watchers trigger events when there are no other events are pending |
643 | periodic) events pending. That is, as long as your process is busy |
647 | (prepare, check and other idle watchers do not count). That is, as long |
644 | handling sockets or timeouts it will not be called. But when your process |
648 | as your process is busy handling sockets or timeouts (or even signals, |
645 | is idle all idle watchers are being called again and again - until |
649 | imagine) it will not be triggered. But when your process is idle all idle |
|
|
650 | watchers are being called again and again, once per event loop iteration - |
646 | stopped, that is, or your process receives more events. |
651 | until stopped, that is, or your process receives more events and becomes |
|
|
652 | busy. |
647 | |
653 | |
648 | The most noteworthy effect is that as long as any idle watchers are |
654 | The most noteworthy effect is that as long as any idle watchers are |
649 | active, the process will not block when waiting for new events. |
655 | active, the process will not block when waiting for new events. |
650 | |
656 | |
651 | Apart from keeping your process non-blocking (which is a useful |
657 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
661 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
667 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
662 | believe me. |
668 | believe me. |
663 | |
669 | |
664 | =back |
670 | =back |
665 | |
671 | |
666 | =head2 prepare and check - your hooks into the event loop |
672 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
667 | |
673 | |
668 | Prepare and check watchers usually (but not always) are used in |
674 | Prepare and check watchers are usually (but not always) used in tandem: |
669 | tandom. Prepare watchers get invoked before the process blocks and check |
675 | Prepare watchers get invoked before the process blocks and check watchers |
670 | watchers afterwards. |
676 | afterwards. |
671 | |
677 | |
672 | Their main purpose is to integrate other event mechanisms into libev. This |
678 | Their main purpose is to integrate other event mechanisms into libev. This |
673 | could be used, for example, to track variable changes, implement your own |
679 | could be used, for example, to track variable changes, implement your own |
674 | watchers, integrate net-snmp or a coroutine library and lots more. |
680 | watchers, integrate net-snmp or a coroutine library and lots more. |
675 | |
681 | |
676 | This is done by examining in each prepare call which file descriptors need |
682 | This is done by examining in each prepare call which file descriptors need |
677 | to be watched by the other library, registering ev_io watchers for them |
683 | to be watched by the other library, registering C<ev_io> watchers for |
678 | and starting an ev_timer watcher for any timeouts (many libraries provide |
684 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
679 | just this functionality). Then, in the check watcher you check for any |
685 | provide just this functionality). Then, in the check watcher you check for |
680 | events that occured (by making your callbacks set soem flags for example) |
686 | any events that occured (by checking the pending status of all watchers |
681 | and call back into the library. |
687 | and stopping them) and call back into the library. The I/O and timer |
|
|
688 | callbacks will never actually be called (but must be valid neverthelles, |
|
|
689 | because you never know, you know?). |
682 | |
690 | |
683 | As another example, the perl Coro module uses these hooks to integrate |
691 | As another example, the Perl Coro module uses these hooks to integrate |
684 | coroutines into libev programs, by yielding to other active coroutines |
692 | coroutines into libev programs, by yielding to other active coroutines |
685 | during each prepare and only letting the process block if no coroutines |
693 | during each prepare and only letting the process block if no coroutines |
686 | are ready to run. |
694 | are ready to run (its actually more complicated, it only runs coroutines |
|
|
695 | with priority higher than the event loop and one lower priority once, |
|
|
696 | using idle watchers to keep the event loop from blocking if lower-priority |
|
|
697 | coroutines exist, thus mapping low-priority coroutines to idle/background |
|
|
698 | tasks). |
687 | |
699 | |
688 | =over 4 |
700 | =over 4 |
689 | |
701 | |
690 | =item ev_prepare_init (ev_prepare *, callback) |
702 | =item ev_prepare_init (ev_prepare *, callback) |
691 | |
703 | |
692 | =item ev_check_init (ev_check *, callback) |
704 | =item ev_check_init (ev_check *, callback) |
693 | |
705 | |
694 | Initialises and configures the prepare or check watcher - they have no |
706 | Initialises and configures the prepare or check watcher - they have no |
695 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
707 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
696 | macros, but using them is utterly, utterly pointless. |
708 | macros, but using them is utterly, utterly and completely pointless. |
697 | |
709 | |
698 | =back |
710 | =back |
699 | |
711 | |
700 | =head1 OTHER FUNCTIONS |
712 | =head1 OTHER FUNCTIONS |
701 | |
713 | |
702 | There are some other fucntions of possible interest. Described. Here. Now. |
714 | There are some other functions of possible interest. Described. Here. Now. |
703 | |
715 | |
704 | =over 4 |
716 | =over 4 |
705 | |
717 | |
706 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
718 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
707 | |
719 | |
… | |
… | |
709 | callback on whichever event happens first and automatically stop both |
721 | callback on whichever event happens first and automatically stop both |
710 | watchers. This is useful if you want to wait for a single event on an fd |
722 | watchers. This is useful if you want to wait for a single event on an fd |
711 | or timeout without havign to allocate/configure/start/stop/free one or |
723 | or timeout without havign to allocate/configure/start/stop/free one or |
712 | more watchers yourself. |
724 | more watchers yourself. |
713 | |
725 | |
714 | If C<fd> is less than 0, then no I/O watcher will be started and events is |
726 | If C<fd> is less than 0, then no I/O watcher will be started and events |
715 | ignored. Otherwise, an ev_io watcher for the given C<fd> and C<events> set |
727 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
716 | will be craeted and started. |
728 | C<events> set will be craeted and started. |
717 | |
729 | |
718 | If C<timeout> is less than 0, then no timeout watcher will be |
730 | If C<timeout> is less than 0, then no timeout watcher will be |
719 | started. Otherwise an ev_timer watcher with after = C<timeout> (and repeat |
731 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
720 | = 0) will be started. |
732 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
|
|
733 | dubious value. |
721 | |
734 | |
722 | The callback has the type C<void (*cb)(int revents, void *arg)> and |
735 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
723 | gets passed an events set (normally a combination of EV_ERROR, EV_READ, |
736 | passed an events set like normal event callbacks (with a combination of |
724 | EV_WRITE or EV_TIMEOUT) and the C<arg> value passed to C<ev_once>: |
737 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
|
|
738 | value passed to C<ev_once>: |
725 | |
739 | |
726 | static void stdin_ready (int revents, void *arg) |
740 | static void stdin_ready (int revents, void *arg) |
727 | { |
741 | { |
728 | if (revents & EV_TIMEOUT) |
742 | if (revents & EV_TIMEOUT) |
729 | /* doh, nothing entered */ |
743 | /* doh, nothing entered */; |
730 | else if (revents & EV_READ) |
744 | else if (revents & EV_READ) |
731 | /* stdin might have data for us, joy! */ |
745 | /* stdin might have data for us, joy! */; |
732 | } |
746 | } |
733 | |
747 | |
734 | ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); |
748 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
735 | |
749 | |
736 | =item ev_feed_event (loop, watcher, int events) |
750 | =item ev_feed_event (loop, watcher, int events) |
737 | |
751 | |
738 | Feeds the given event set into the event loop, as if the specified event |
752 | Feeds the given event set into the event loop, as if the specified event |
739 | has happened for the specified watcher (which must be a pointer to an |
753 | had happened for the specified watcher (which must be a pointer to an |
740 | initialised but not necessarily active event watcher). |
754 | initialised but not necessarily started event watcher). |
741 | |
755 | |
742 | =item ev_feed_fd_event (loop, int fd, int revents) |
756 | =item ev_feed_fd_event (loop, int fd, int revents) |
743 | |
757 | |
744 | Feed an event on the given fd, as if a file descriptor backend detected it. |
758 | Feed an event on the given fd, as if a file descriptor backend detected |
|
|
759 | the given events it. |
745 | |
760 | |
746 | =item ev_feed_signal_event (loop, int signum) |
761 | =item ev_feed_signal_event (loop, int signum) |
747 | |
762 | |
748 | Feed an event as if the given signal occured (loop must be the default loop!). |
763 | Feed an event as if the given signal occured (loop must be the default loop!). |
749 | |
764 | |