… | |
… | |
39 | F<README.embed> in the libev distribution. If libev was configured without |
39 | F<README.embed> in the libev distribution. If libev was configured without |
40 | support for multiple event loops, then all functions taking an initial |
40 | support for multiple event loops, then all functions taking an initial |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
42 | will not have this argument. |
42 | will not have this argument. |
43 | |
43 | |
44 | =head1 TIME AND OTHER GLOBAL FUNCTIONS |
44 | =head1 TIME REPRESENTATION |
45 | |
45 | |
46 | Libev represents time as a single floating point number, representing the |
46 | Libev represents time as a single floating point number, representing the |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
50 | to the double type in C. |
50 | to the double type in C. |
51 | |
51 | |
|
|
52 | =head1 GLOBAL FUNCTIONS |
|
|
53 | |
|
|
54 | These functions can be called anytime, even before initialising the |
|
|
55 | library in any way. |
|
|
56 | |
52 | =over 4 |
57 | =over 4 |
53 | |
58 | |
54 | =item ev_tstamp ev_time () |
59 | =item ev_tstamp ev_time () |
55 | |
60 | |
56 | Returns the current time as libev would use it. |
61 | Returns the current time as libev would use it. Please note that the |
|
|
62 | C<ev_now> function is usually faster and also often returns the timestamp |
|
|
63 | you actually want to know. |
57 | |
64 | |
58 | =item int ev_version_major () |
65 | =item int ev_version_major () |
59 | |
66 | |
60 | =item int ev_version_minor () |
67 | =item int ev_version_minor () |
61 | |
68 | |
… | |
… | |
99 | An event loop is described by a C<struct ev_loop *>. The library knows two |
106 | An event loop is described by a C<struct ev_loop *>. The library knows two |
100 | types of such loops, the I<default> loop, which supports signals and child |
107 | types of such loops, the I<default> loop, which supports signals and child |
101 | events, and dynamically created loops which do not. |
108 | events, and dynamically created loops which do not. |
102 | |
109 | |
103 | If you use threads, a common model is to run the default event loop |
110 | If you use threads, a common model is to run the default event loop |
104 | in your main thread (or in a separate thrad) and for each thread you |
111 | in your main thread (or in a separate thread) and for each thread you |
105 | create, you also create another event loop. Libev itself does no locking |
112 | create, you also create another event loop. Libev itself does no locking |
106 | whatsoever, so if you mix calls to the same event loop in different |
113 | whatsoever, so if you mix calls to the same event loop in different |
107 | threads, make sure you lock (this is usually a bad idea, though, even if |
114 | threads, make sure you lock (this is usually a bad idea, though, even if |
108 | done correctly, because it's hideous and inefficient). |
115 | done correctly, because it's hideous and inefficient). |
109 | |
116 | |
… | |
… | |
236 | |
243 | |
237 | =item ev_unloop (loop, how) |
244 | =item ev_unloop (loop, how) |
238 | |
245 | |
239 | Can be used to make a call to C<ev_loop> return early (but only after it |
246 | Can be used to make a call to C<ev_loop> return early (but only after it |
240 | has processed all outstanding events). The C<how> argument must be either |
247 | has processed all outstanding events). The C<how> argument must be either |
241 | C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop> call return, or |
248 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
242 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
249 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
243 | |
250 | |
244 | =item ev_ref (loop) |
251 | =item ev_ref (loop) |
245 | |
252 | |
246 | =item ev_unref (loop) |
253 | =item ev_unref (loop) |
… | |
… | |
299 | |
306 | |
300 | As long as your watcher is active (has been started but not stopped) you |
307 | 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 |
308 | must not touch the values stored in it. Most specifically you must never |
302 | reinitialise it or call its set method. |
309 | reinitialise it or call its set method. |
303 | |
310 | |
304 | You cna check whether an event is active by calling the C<ev_is_active |
311 | 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 |
312 | (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 |
313 | callback for it has not been called yet) you can use the C<ev_is_pending |
307 | (watcher *)> macro. |
314 | (watcher *)> macro. |
308 | |
315 | |
309 | Each and every callback receives the event loop pointer as first, the |
316 | 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 |
317 | registered watcher structure as second, and a bitset of received events as |
311 | third argument. |
318 | third argument. |
312 | |
319 | |
313 | The rceeived events usually include a single bit per event type received |
320 | 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 |
321 | (you can receive multiple events at the same time). The possible bit masks |
315 | are: |
322 | are: |
316 | |
323 | |
317 | =over 4 |
324 | =over 4 |
318 | |
325 | |
… | |
… | |
372 | =back |
379 | =back |
373 | |
380 | |
374 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
381 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
375 | |
382 | |
376 | Each watcher has, by default, a member C<void *data> that you can change |
383 | 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 |
384 | 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 |
385 | 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 |
386 | 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 |
387 | member, you can also "subclass" the watcher type and provide your own |
381 | data: |
388 | data: |
382 | |
389 | |
… | |
… | |
409 | =head2 C<ev_io> - is this file descriptor readable or writable |
416 | =head2 C<ev_io> - is this file descriptor readable or writable |
410 | |
417 | |
411 | I/O watchers check whether a file descriptor is readable or writable |
418 | I/O watchers check whether a file descriptor is readable or writable |
412 | in each iteration of the event loop (This behaviour is called |
419 | in each iteration of the event loop (This behaviour is called |
413 | level-triggering because you keep receiving events as long as the |
420 | 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 |
421 | 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). |
422 | act on the event and neither want to receive future events). |
416 | |
423 | |
417 | In general you can register as many read and/or write event watchers oer |
424 | In general you can register as many read and/or write event watchers per |
418 | fd as you want (as long as you don't confuse yourself). Setting all file |
425 | 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 |
426 | descriptors to non-blocking mode is also usually a good idea (but not |
420 | required if you know what you are doing). |
427 | required if you know what you are doing). |
421 | |
428 | |
422 | You have to be careful with dup'ed file descriptors, though. Some backends |
429 | You have to be careful with dup'ed file descriptors, though. Some backends |
423 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
430 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
424 | descriptors correctly if you register interest in two or more fds pointing |
431 | descriptors correctly if you register interest in two or more fds pointing |
425 | to the same file/socket etc. description. |
432 | to the same underlying file/socket etc. description (that is, they share |
|
|
433 | the same underlying "file open"). |
426 | |
434 | |
427 | If you must do this, then force the use of a known-to-be-good backend |
435 | If you must do this, then force the use of a known-to-be-good backend |
428 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
436 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
429 | EVMETHOD_POLL). |
437 | EVMETHOD_POLL). |
430 | |
438 | |
… | |
… | |
444 | |
452 | |
445 | Timer watchers are simple relative timers that generate an event after a |
453 | Timer watchers are simple relative timers that generate an event after a |
446 | given time, and optionally repeating in regular intervals after that. |
454 | given time, and optionally repeating in regular intervals after that. |
447 | |
455 | |
448 | The timers are based on real time, that is, if you register an event that |
456 | The timers are based on real time, that is, if you register an event that |
449 | times out after an hour and youreset your system clock to last years |
457 | times out after an hour and you reset your system clock to last years |
450 | time, it will still time out after (roughly) and hour. "Roughly" because |
458 | time, it will still time out after (roughly) and hour. "Roughly" because |
451 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
459 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
452 | monotonic clock option helps a lot here). |
460 | monotonic clock option helps a lot here). |
453 | |
461 | |
454 | The relative timeouts are calculated relative to the C<ev_now ()> |
462 | The relative timeouts are calculated relative to the C<ev_now ()> |
455 | time. This is usually the right thing as this timestamp refers to the time |
463 | time. This is usually the right thing as this timestamp refers to the time |
456 | of the event triggering whatever timeout you are modifying/starting. If |
464 | of the event triggering whatever timeout you are modifying/starting. If |
457 | you suspect event processing to be delayed and you *need* to base the timeout |
465 | you suspect event processing to be delayed and you *need* to base the timeout |
458 | ion the current time, use something like this to adjust for this: |
466 | on the current time, use something like this to adjust for this: |
459 | |
467 | |
460 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
468 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
461 | |
469 | |
462 | =over 4 |
470 | =over 4 |
463 | |
471 | |
… | |
… | |
471 | later, again, and again, until stopped manually. |
479 | later, again, and again, until stopped manually. |
472 | |
480 | |
473 | The timer itself will do a best-effort at avoiding drift, that is, if you |
481 | The timer itself will do a best-effort at avoiding drift, that is, if you |
474 | configure a timer to trigger every 10 seconds, then it will trigger at |
482 | configure a timer to trigger every 10 seconds, then it will trigger at |
475 | exactly 10 second intervals. If, however, your program cannot keep up with |
483 | exactly 10 second intervals. If, however, your program cannot keep up with |
476 | the timer (ecause it takes longer than those 10 seconds to do stuff) the |
484 | the timer (because it takes longer than those 10 seconds to do stuff) the |
477 | timer will not fire more than once per event loop iteration. |
485 | timer will not fire more than once per event loop iteration. |
478 | |
486 | |
479 | =item ev_timer_again (loop) |
487 | =item ev_timer_again (loop) |
480 | |
488 | |
481 | This will act as if the timer timed out and restart it again if it is |
489 | This will act as if the timer timed out and restart it again if it is |
… | |
… | |
495 | state where you do not expect data to travel on the socket, you can stop |
503 | 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. |
504 | the timer, and again will automatically restart it if need be. |
497 | |
505 | |
498 | =back |
506 | =back |
499 | |
507 | |
500 | =head2 C<ev_periodic> - to cron or not to cron it |
508 | =head2 C<ev_periodic> - to cron or not to cron |
501 | |
509 | |
502 | Periodic watchers are also timers of a kind, but they are very versatile |
510 | Periodic watchers are also timers of a kind, but they are very versatile |
503 | (and unfortunately a bit complex). |
511 | (and unfortunately a bit complex). |
504 | |
512 | |
505 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
513 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
… | |
… | |
544 | |
552 | |
545 | ev_periodic_set (&periodic, 0., 3600., 0); |
553 | ev_periodic_set (&periodic, 0., 3600., 0); |
546 | |
554 | |
547 | This doesn't mean there will always be 3600 seconds in between triggers, |
555 | 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 |
556 | 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 |
557 | full hour (UTC), or more correctly, when the system time is evenly divisible |
550 | by 3600. |
558 | by 3600. |
551 | |
559 | |
552 | Another way to think about it (for the mathematically inclined) is that |
560 | Another way to think about it (for the mathematically inclined) is that |
553 | C<ev_periodic> will try to run the callback in this mode at the next possible |
561 | 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. |
562 | time where C<time = at (mod interval)>, regardless of any time jumps. |
… | |
… | |
558 | In this mode the values for C<interval> and C<at> are both being |
566 | 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 |
567 | ignored. Instead, each time the periodic watcher gets scheduled, the |
560 | reschedule callback will be called with the watcher as first, and the |
568 | reschedule callback will be called with the watcher as first, and the |
561 | current time as second argument. |
569 | current time as second argument. |
562 | |
570 | |
563 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
571 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
564 | periodic watcher, ever, or make any event loop modificstions>. If you need |
572 | ever, or make any event loop modifications>. If you need to stop it, |
565 | to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards. |
573 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
|
|
574 | starting a prepare watcher). |
566 | |
575 | |
567 | Its prototype is c<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
576 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
568 | ev_tstamp now)>, e.g.: |
577 | ev_tstamp now)>, e.g.: |
569 | |
578 | |
570 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
579 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
571 | { |
580 | { |
572 | return now + 60.; |
581 | return now + 60.; |
… | |
… | |
575 | It must return the next time to trigger, based on the passed time value |
584 | It must return the next time to trigger, based on the passed time value |
576 | (that is, the lowest time value larger than to the second argument). It |
585 | (that is, the lowest time value larger than to the second argument). It |
577 | will usually be called just before the callback will be triggered, but |
586 | will usually be called just before the callback will be triggered, but |
578 | might be called at other times, too. |
587 | might be called at other times, too. |
579 | |
588 | |
|
|
589 | NOTE: I<< This callback must always return a time that is later than the |
|
|
590 | passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger. |
|
|
591 | |
580 | This can be used to create very complex timers, such as a timer that |
592 | This can be used to create very complex timers, such as a timer that |
581 | triggers on each midnight, local time. To do this, you would calculate the |
593 | triggers on each midnight, local time. To do this, you would calculate the |
582 | next midnight after C<now> and return the timestamp value for this. How you do this |
594 | next midnight after C<now> and return the timestamp value for this. How |
583 | is, again, up to you (but it is not trivial). |
595 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
596 | reason I omitted it as an example). |
584 | |
597 | |
585 | =back |
598 | =back |
586 | |
599 | |
587 | =item ev_periodic_again (loop, ev_periodic *) |
600 | =item ev_periodic_again (loop, ev_periodic *) |
588 | |
601 | |
… | |
… | |
598 | Signal watchers will trigger an event when the process receives a specific |
611 | 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 |
612 | 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 |
613 | will try it's best to deliver signals synchronously, i.e. as part of the |
601 | normal event processing, like any other event. |
614 | normal event processing, like any other event. |
602 | |
615 | |
603 | You cna configure as many watchers as you like per signal. Only when the |
616 | 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 |
617 | 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 |
618 | 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 |
619 | 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 |
620 | watcher for a signal is stopped libev will reset the signal handler to |
608 | SIG_DFL (regardless of what it was set to before). |
621 | SIG_DFL (regardless of what it was set to before). |
… | |
… | |
630 | =item ev_child_set (ev_child *, int pid) |
643 | =item ev_child_set (ev_child *, int pid) |
631 | |
644 | |
632 | Configures the watcher to wait for status changes of process C<pid> (or |
645 | 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 |
646 | 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 |
647 | 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 |
648 | 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. |
649 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
|
|
650 | process causing the status change. |
637 | |
651 | |
638 | =back |
652 | =back |
639 | |
653 | |
640 | =head2 C<ev_idle> - when you've got nothing better to do |
654 | =head2 C<ev_idle> - when you've got nothing better to do |
641 | |
655 | |
642 | Idle watchers trigger events when there are no other I/O or timer (or |
656 | 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 |
657 | (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 |
658 | 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 |
659 | imagine) it will not be triggered. But when your process is idle all idle |
|
|
660 | watchers are being called again and again, once per event loop iteration - |
646 | stopped, that is, or your process receives more events. |
661 | until stopped, that is, or your process receives more events and becomes |
|
|
662 | busy. |
647 | |
663 | |
648 | The most noteworthy effect is that as long as any idle watchers are |
664 | 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. |
665 | active, the process will not block when waiting for new events. |
650 | |
666 | |
651 | Apart from keeping your process non-blocking (which is a useful |
667 | 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, |
677 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
662 | believe me. |
678 | believe me. |
663 | |
679 | |
664 | =back |
680 | =back |
665 | |
681 | |
666 | =head2 prepare and check - your hooks into the event loop |
682 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
667 | |
683 | |
668 | Prepare and check watchers usually (but not always) are used in |
684 | Prepare and check watchers are usually (but not always) used in tandem: |
669 | tandom. Prepare watchers get invoked before the process blocks and check |
685 | prepare watchers get invoked before the process blocks and check watchers |
670 | watchers afterwards. |
686 | afterwards. |
671 | |
687 | |
672 | Their main purpose is to integrate other event mechanisms into libev. This |
688 | 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 |
689 | could be used, for example, to track variable changes, implement your own |
674 | watchers, integrate net-snmp or a coroutine library and lots more. |
690 | watchers, integrate net-snmp or a coroutine library and lots more. |
675 | |
691 | |
676 | This is done by examining in each prepare call which file descriptors need |
692 | This is done by examining in each prepare call which file descriptors need |
677 | to be watched by the other library, registering C<ev_io> watchers for them |
693 | to be watched by the other library, registering C<ev_io> watchers for |
678 | and starting an C<ev_timer> watcher for any timeouts (many libraries provide |
694 | 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 |
695 | 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) |
696 | any events that occured (by checking the pending status of all watchers |
681 | and call back into the library. |
697 | and stopping them) and call back into the library. The I/O and timer |
|
|
698 | callbacks will never actually be called (but must be valid nevertheless, |
|
|
699 | because you never know, you know?). |
682 | |
700 | |
683 | As another example, the perl Coro module uses these hooks to integrate |
701 | As another example, the Perl Coro module uses these hooks to integrate |
684 | coroutines into libev programs, by yielding to other active coroutines |
702 | coroutines into libev programs, by yielding to other active coroutines |
685 | during each prepare and only letting the process block if no coroutines |
703 | during each prepare and only letting the process block if no coroutines |
686 | are ready to run. |
704 | are ready to run (it's actually more complicated: it only runs coroutines |
|
|
705 | with priority higher than or equal to the event loop and one coroutine |
|
|
706 | of lower priority, but only once, using idle watchers to keep the event |
|
|
707 | loop from blocking if lower-priority coroutines are active, thus mapping |
|
|
708 | low-priority coroutines to idle/background tasks). |
687 | |
709 | |
688 | =over 4 |
710 | =over 4 |
689 | |
711 | |
690 | =item ev_prepare_init (ev_prepare *, callback) |
712 | =item ev_prepare_init (ev_prepare *, callback) |
691 | |
713 | |
692 | =item ev_check_init (ev_check *, callback) |
714 | =item ev_check_init (ev_check *, callback) |
693 | |
715 | |
694 | Initialises and configures the prepare or check watcher - they have no |
716 | 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> |
717 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
696 | macros, but using them is utterly, utterly pointless. |
718 | macros, but using them is utterly, utterly and completely pointless. |
697 | |
719 | |
698 | =back |
720 | =back |
699 | |
721 | |
700 | =head1 OTHER FUNCTIONS |
722 | =head1 OTHER FUNCTIONS |
701 | |
723 | |
702 | There are some other fucntions of possible interest. Described. Here. Now. |
724 | There are some other functions of possible interest. Described. Here. Now. |
703 | |
725 | |
704 | =over 4 |
726 | =over 4 |
705 | |
727 | |
706 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
728 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
707 | |
729 | |
708 | This function combines a simple timer and an I/O watcher, calls your |
730 | This function combines a simple timer and an I/O watcher, calls your |
709 | callback on whichever event happens first and automatically stop both |
731 | 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 |
732 | 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 |
733 | or timeout without having to allocate/configure/start/stop/free one or |
712 | more watchers yourself. |
734 | more watchers yourself. |
713 | |
735 | |
714 | If C<fd> is less than 0, then no I/O watcher will be started and events is |
736 | If C<fd> is less than 0, then no I/O watcher will be started and events |
715 | ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and C<events> set |
737 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
716 | will be craeted and started. |
738 | C<events> set will be craeted and started. |
717 | |
739 | |
718 | If C<timeout> is less than 0, then no timeout watcher will be |
740 | If C<timeout> is less than 0, then no timeout watcher will be |
719 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and repeat |
741 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
720 | = 0) will be started. |
742 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
|
|
743 | dubious value. |
721 | |
744 | |
722 | The callback has the type C<void (*cb)(int revents, void *arg)> and |
745 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
723 | gets passed an events set (normally a combination of C<EV_ERROR>, C<EV_READ>, |
746 | passed an C<revents> set like normal event callbacks (a combination of |
724 | C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> value passed to C<ev_once>: |
747 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
|
|
748 | value passed to C<ev_once>: |
725 | |
749 | |
726 | static void stdin_ready (int revents, void *arg) |
750 | static void stdin_ready (int revents, void *arg) |
727 | { |
751 | { |
728 | if (revents & EV_TIMEOUT) |
752 | if (revents & EV_TIMEOUT) |
729 | /* doh, nothing entered */ |
753 | /* doh, nothing entered */; |
730 | else if (revents & EV_READ) |
754 | else if (revents & EV_READ) |
731 | /* stdin might have data for us, joy! */ |
755 | /* stdin might have data for us, joy! */; |
732 | } |
756 | } |
733 | |
757 | |
734 | ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); |
758 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
735 | |
759 | |
736 | =item ev_feed_event (loop, watcher, int events) |
760 | =item ev_feed_event (loop, watcher, int events) |
737 | |
761 | |
738 | Feeds the given event set into the event loop, as if the specified event |
762 | 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 |
763 | had happened for the specified watcher (which must be a pointer to an |
740 | initialised but not necessarily active event watcher). |
764 | initialised but not necessarily started event watcher). |
741 | |
765 | |
742 | =item ev_feed_fd_event (loop, int fd, int revents) |
766 | =item ev_feed_fd_event (loop, int fd, int revents) |
743 | |
767 | |
744 | Feed an event on the given fd, as if a file descriptor backend detected it. |
768 | Feed an event on the given fd, as if a file descriptor backend detected |
|
|
769 | the given events it. |
745 | |
770 | |
746 | =item ev_feed_signal_event (loop, int signum) |
771 | =item ev_feed_signal_event (loop, int signum) |
747 | |
772 | |
748 | Feed an event as if the given signal occured (loop must be the default loop!). |
773 | Feed an event as if the given signal occured (loop must be the default loop!). |
749 | |
774 | |
750 | =back |
775 | =back |
751 | |
776 | |
|
|
777 | =head1 LIBEVENT EMULATION |
|
|
778 | |
|
|
779 | Libev offers a compatibility emulation layer for libevent. It cannot |
|
|
780 | emulate the internals of libevent, so here are some usage hints: |
|
|
781 | |
|
|
782 | =over 4 |
|
|
783 | |
|
|
784 | =item * Use it by including <event.h>, as usual. |
|
|
785 | |
|
|
786 | =item * The following members are fully supported: ev_base, ev_callback, |
|
|
787 | ev_arg, ev_fd, ev_res, ev_events. |
|
|
788 | |
|
|
789 | =item * Avoid using ev_flags and the EVLIST_*-macros, while it is |
|
|
790 | maintained by libev, it does not work exactly the same way as in libevent (consider |
|
|
791 | it a private API). |
|
|
792 | |
|
|
793 | =item * Priorities are not currently supported. Initialising priorities |
|
|
794 | will fail and all watchers will have the same priority, even though there |
|
|
795 | is an ev_pri field. |
|
|
796 | |
|
|
797 | =item * Other members are not supported. |
|
|
798 | |
|
|
799 | =item * The libev emulation is I<not> ABI compatible to libevent, you need |
|
|
800 | to use the libev header file and library. |
|
|
801 | |
|
|
802 | =back |
|
|
803 | |
|
|
804 | =head1 C++ SUPPORT |
|
|
805 | |
|
|
806 | TBD. |
|
|
807 | |
752 | =head1 AUTHOR |
808 | =head1 AUTHOR |
753 | |
809 | |
754 | Marc Lehmann <libev@schmorp.de>. |
810 | Marc Lehmann <libev@schmorp.de>. |
755 | |
811 | |