| 1 | libev is modelled after libevent (http://monkey.org/~provos/libevent/), but aims |
1 | libev is modelled (very losely) after libevent |
|
|
2 | (http://monkey.org/~provos/libevent/), but aims to be faster and more |
| 2 | to be faster and more correct, and also more featureful. Examples: |
3 | correct, and also more featureful. Examples: |
| 3 | |
4 | |
| 4 | (comparisons relative to libevent-1.3e and libev-0.00) |
5 | (comparisons relative to libevent-1.3e and libev-0.00) |
| 5 | |
6 | |
| 6 | - multiple watchers can wait for the same event without deregistering others, |
7 | - multiple watchers can wait for the same event without deregistering others, |
| 7 | both for file descriptors as well as signals. |
8 | both for file descriptors as well as signals. |
| … | |
… | |
| 9 | break the other) |
10 | break the other) |
| 10 | |
11 | |
| 11 | - fork() is supported and can be handled |
12 | - fork() is supported and can be handled |
| 12 | (there is no way to recover from a fork when libevent is active) |
13 | (there is no way to recover from a fork when libevent is active) |
| 13 | |
14 | |
| 14 | - timers are handled as a priority queue |
15 | - timers are handled as a priority queue (important operations are O(1)) |
| 15 | (libevent uses a less efficient red-black tree) |
16 | (libevent uses a much less efficient but more complex red-black tree) |
| 16 | |
17 | |
| 17 | - supports absolute (wallclock-based) timers in addition to relative ones, |
18 | - supports absolute (wallclock-based) timers in addition to relative ones, |
| 18 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
19 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
| 19 | |
20 | |
| 20 | - timers can be repeating (both absolute and relative ones) |
21 | - timers can be repeating (both absolute and relative ones) |
| … | |
… | |
| 52 | |
53 | |
| 53 | - simpler design, backends are potentially much simpler |
54 | - simpler design, backends are potentially much simpler |
| 54 | (in libevent, backends have to deal with watchers, thus the problems) |
55 | (in libevent, backends have to deal with watchers, thus the problems) |
| 55 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) |
56 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) |
| 56 | |
57 | |
|
|
58 | - libev handles EBADF gracefully by removing the offending fds. |
|
|
59 | |
|
|
60 | - doesn't rely on nonportable BSD header files. |
|
|
61 | |
| 57 | whats missing? |
62 | whats missing? |
| 58 | |
63 | |
| 59 | - evdns, evhttp, bufferevent are missing, libev is only an even library at |
64 | - evdns, evhttp, bufferevent are missing, libev is only an even library at |
| 60 | the moment. |
65 | the moment. |
| 61 | |
66 | |
