| … | |
… | |
| 63 | details of the event, and then hand it over to libev by I<starting> the |
63 | details of the event, and then hand it over to libev by I<starting> the |
| 64 | watcher. |
64 | watcher. |
| 65 | |
65 | |
| 66 | =head1 FEATURES |
66 | =head1 FEATURES |
| 67 | |
67 | |
| 68 | Libev supports C<select>, C<poll>, the linux-specific C<epoll>, the |
68 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
| 69 | bsd-specific C<kqueue> and the solaris-specific event port mechanisms |
69 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
| 70 | for file descriptor events (C<ev_io>), relative timers (C<ev_timer>), |
70 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
|
|
71 | (for C<ev_stat>), relative timers (C<ev_timer>), absolute timers |
| 71 | absolute timers with customised rescheduling (C<ev_periodic>), synchronous |
72 | with customised rescheduling (C<ev_periodic>), synchronous signals |
| 72 | signals (C<ev_signal>), process status change events (C<ev_child>), and |
73 | (C<ev_signal>), process status change events (C<ev_child>), and event |
| 73 | event watchers dealing with the event loop mechanism itself (C<ev_idle>, |
74 | watchers dealing with the event loop mechanism itself (C<ev_idle>, |
| 74 | C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as |
75 | C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as |
| 75 | file watchers (C<ev_stat>) and even limited support for fork events |
76 | file watchers (C<ev_stat>) and even limited support for fork events |
| 76 | (C<ev_fork>). |
77 | (C<ev_fork>). |
| 77 | |
78 | |
| 78 | It also is quite fast (see this |
79 | It also is quite fast (see this |
