… | |
… | |
425 | required if you know what you are doing). |
425 | required if you know what you are doing). |
426 | |
426 | |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
428 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
428 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
429 | descriptors correctly if you register interest in two or more fds pointing |
429 | descriptors correctly if you register interest in two or more fds pointing |
430 | to the same file/socket etc. description. |
430 | to the same file/socket etc. description (that is, they share the same |
|
|
431 | underlying "file open"). |
431 | |
432 | |
432 | If you must do this, then force the use of a known-to-be-good backend |
433 | If you must do this, then force the use of a known-to-be-good backend |
433 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | EVMETHOD_POLL). |
435 | EVMETHOD_POLL). |
435 | |
436 | |
… | |
… | |
449 | |
450 | |
450 | Timer watchers are simple relative timers that generate an event after a |
451 | Timer watchers are simple relative timers that generate an event after a |
451 | given time, and optionally repeating in regular intervals after that. |
452 | given time, and optionally repeating in regular intervals after that. |
452 | |
453 | |
453 | The timers are based on real time, that is, if you register an event that |
454 | The timers are based on real time, that is, if you register an event that |
454 | times out after an hour and youreset your system clock to last years |
455 | times out after an hour and you reset your system clock to last years |
455 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | monotonic clock option helps a lot here). |
458 | monotonic clock option helps a lot here). |
458 | |
459 | |
459 | The relative timeouts are calculated relative to the C<ev_now ()> |
460 | The relative timeouts are calculated relative to the C<ev_now ()> |
460 | time. This is usually the right thing as this timestamp refers to the time |
461 | time. This is usually the right thing as this timestamp refers to the time |
461 | of the event triggering whatever timeout you are modifying/starting. If |
462 | of the event triggering whatever timeout you are modifying/starting. If |
462 | you suspect event processing to be delayed and you *need* to base the timeout |
463 | you suspect event processing to be delayed and you *need* to base the timeout |
463 | ion the current time, use something like this to adjust for this: |
464 | on the current time, use something like this to adjust for this: |
464 | |
465 | |
465 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
466 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
466 | |
467 | |
467 | =over 4 |
468 | =over 4 |
468 | |
469 | |
… | |
… | |
476 | later, again, and again, until stopped manually. |
477 | later, again, and again, until stopped manually. |
477 | |
478 | |
478 | The timer itself will do a best-effort at avoiding drift, that is, if you |
479 | The timer itself will do a best-effort at avoiding drift, that is, if you |
479 | configure a timer to trigger every 10 seconds, then it will trigger at |
480 | configure a timer to trigger every 10 seconds, then it will trigger at |
480 | exactly 10 second intervals. If, however, your program cannot keep up with |
481 | exactly 10 second intervals. If, however, your program cannot keep up with |
481 | the timer (ecause it takes longer than those 10 seconds to do stuff) the |
482 | the timer (because it takes longer than those 10 seconds to do stuff) the |
482 | timer will not fire more than once per event loop iteration. |
483 | timer will not fire more than once per event loop iteration. |
483 | |
484 | |
484 | =item ev_timer_again (loop) |
485 | =item ev_timer_again (loop) |
485 | |
486 | |
486 | This will act as if the timer timed out and restart it again if it is |
487 | This will act as if the timer timed out and restart it again if it is |
… | |
… | |
725 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
726 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
726 | |
727 | |
727 | This function combines a simple timer and an I/O watcher, calls your |
728 | This function combines a simple timer and an I/O watcher, calls your |
728 | callback on whichever event happens first and automatically stop both |
729 | callback on whichever event happens first and automatically stop both |
729 | watchers. This is useful if you want to wait for a single event on an fd |
730 | watchers. This is useful if you want to wait for a single event on an fd |
730 | or timeout without havign to allocate/configure/start/stop/free one or |
731 | or timeout without having to allocate/configure/start/stop/free one or |
731 | more watchers yourself. |
732 | more watchers yourself. |
732 | |
733 | |
733 | If C<fd> is less than 0, then no I/O watcher will be started and events |
734 | If C<fd> is less than 0, then no I/O watcher will be started and events |
734 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
735 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
735 | C<events> set will be craeted and started. |
736 | C<events> set will be craeted and started. |