… | |
… | |
744 | =item ev_cb_set (ev_TYPE *watcher, callback) |
744 | =item ev_cb_set (ev_TYPE *watcher, callback) |
745 | |
745 | |
746 | Change the callback. You can change the callback at virtually any time |
746 | Change the callback. You can change the callback at virtually any time |
747 | (modulo threads). |
747 | (modulo threads). |
748 | |
748 | |
|
|
749 | =item ev_set_priority (ev_TYPE *watcher, priority) |
|
|
750 | |
|
|
751 | =item int ev_priority (ev_TYPE *watcher) |
|
|
752 | |
|
|
753 | Set and query the priority of the watcher. The priority is a small |
|
|
754 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
|
|
755 | (default: C<-2>). Pending watchers with higher priority will be invoked |
|
|
756 | before watchers with lower priority, but priority will not keep watchers |
|
|
757 | from being executed (except for C<ev_idle> watchers). |
|
|
758 | |
|
|
759 | This means that priorities are I<only> used for ordering callback |
|
|
760 | invocation after new events have been received. This is useful, for |
|
|
761 | example, to reduce latency after idling, or more often, to bind two |
|
|
762 | watchers on the same event and make sure one is called first. |
|
|
763 | |
|
|
764 | If you need to suppress invocation when higher priority events are pending |
|
|
765 | you need to look at C<ev_idle> watchers, which provide this functionality. |
|
|
766 | |
|
|
767 | The default priority used by watchers when no priority has been set is |
|
|
768 | always C<0>, which is supposed to not be too high and not be too low :). |
|
|
769 | |
|
|
770 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
|
|
771 | fine, as long as you do not mind that the priority value you query might |
|
|
772 | or might not have been adjusted to be within valid range. |
|
|
773 | |
749 | =back |
774 | =back |
750 | |
775 | |
751 | |
776 | |
752 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
777 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
753 | |
778 | |
… | |
… | |
1351 | ev_stat_start (loop, &passwd); |
1376 | ev_stat_start (loop, &passwd); |
1352 | |
1377 | |
1353 | |
1378 | |
1354 | =head2 C<ev_idle> - when you've got nothing better to do... |
1379 | =head2 C<ev_idle> - when you've got nothing better to do... |
1355 | |
1380 | |
1356 | Idle watchers trigger events when there are no other events are pending |
1381 | Idle watchers trigger events when no other events of the same or higher |
1357 | (prepare, check and other idle watchers do not count). That is, as long |
1382 | priority are pending (prepare, check and other idle watchers do not |
1358 | as your process is busy handling sockets or timeouts (or even signals, |
1383 | count). |
1359 | imagine) it will not be triggered. But when your process is idle all idle |
1384 | |
1360 | watchers are being called again and again, once per event loop iteration - |
1385 | That is, as long as your process is busy handling sockets or timeouts |
|
|
1386 | (or even signals, imagine) of the same or higher priority it will not be |
|
|
1387 | triggered. But when your process is idle (or only lower-priority watchers |
|
|
1388 | are pending), the idle watchers are being called once per event loop |
1361 | until stopped, that is, or your process receives more events and becomes |
1389 | iteration - until stopped, that is, or your process receives more events |
1362 | busy. |
1390 | and becomes busy again with higher priority stuff. |
1363 | |
1391 | |
1364 | The most noteworthy effect is that as long as any idle watchers are |
1392 | The most noteworthy effect is that as long as any idle watchers are |
1365 | active, the process will not block when waiting for new events. |
1393 | active, the process will not block when waiting for new events. |
1366 | |
1394 | |
1367 | Apart from keeping your process non-blocking (which is a useful |
1395 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
2101 | |
2129 | |
2102 | If undefined or defined to be C<1>, then periodic timers are supported. If |
2130 | If undefined or defined to be C<1>, then periodic timers are supported. If |
2103 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
2131 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
2104 | code. |
2132 | code. |
2105 | |
2133 | |
|
|
2134 | =item EV_IDLE_ENABLE |
|
|
2135 | |
|
|
2136 | If undefined or defined to be C<1>, then idle watchers are supported. If |
|
|
2137 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
|
|
2138 | code. |
|
|
2139 | |
2106 | =item EV_EMBED_ENABLE |
2140 | =item EV_EMBED_ENABLE |
2107 | |
2141 | |
2108 | If undefined or defined to be C<1>, then embed watchers are supported. If |
2142 | If undefined or defined to be C<1>, then embed watchers are supported. If |
2109 | defined to be C<0>, then they are not. |
2143 | defined to be C<0>, then they are not. |
2110 | |
2144 | |