| 1 | libev is modelled after libevent (http://monkey.org/~provos/libevent/), but aims |
1 | libev is modelled after libevent (http://monkey.org/~provos/libevent/), but aims |
| 2 | to be faster and more correct, and also more featureful. Examples: |
2 | to be faster and more correct, and also more featureful. Examples: |
| 3 | |
3 | |
|
|
4 | (comparisons relative to libevent-1.3e and libev-0.00) |
|
|
5 | |
| 4 | - multiple watchers can wait for the same event without deregistering others. |
6 | - multiple watchers can wait for the same event without deregistering others, |
|
|
7 | both for file descriptors as well as signals. |
| 5 | (registering two read events on fd 10 and unregistering one will not |
8 | (registering two read events on fd 10 and unregistering one will not |
| 6 | break the other) |
9 | break the other) |
| 7 | |
10 | |
| 8 | - fork() is supported and can be handled |
11 | - fork() is supported and can be handled |
| 9 | (there is no way to recover from a fork when libevent is active) |
12 | (there is no way to recover from a fork when libevent is active) |
| 10 | |
13 | |
| 11 | - timers are handled as a priority queue |
14 | - timers are handled as a priority queue (important operations are O(1)) |
| 12 | (libevent uses a less efficient red-black tree) |
15 | (libevent uses a much less efficient but more complex red-black tree) |
| 13 | |
16 | |
| 14 | - supports absolute (wallclock-based) timers in addition to relative ones, |
17 | - supports absolute (wallclock-based) timers in addition to relative ones, |
| 15 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
18 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
| 16 | |
19 | |
| 17 | - timers can be repeating (both absolute and relative ones) |
20 | - timers can be repeating (both absolute and relative ones) |
| … | |
… | |
| 47 | (libevent combines them, but with libev you can combine them yourself |
50 | (libevent combines them, but with libev you can combine them yourself |
| 48 | by reusing the same callback and still save memory) |
51 | by reusing the same callback and still save memory) |
| 49 | |
52 | |
| 50 | - simpler design, backends are potentially much simpler |
53 | - simpler design, backends are potentially much simpler |
| 51 | (in libevent, backends have to deal with watchers, thus the problems) |
54 | (in libevent, backends have to deal with watchers, thus the problems) |
| 52 | (epoll backend in libevent: 366 lines, libev: 89 lines, and more features) |
55 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) |
|
|
56 | |
|
|
57 | - libev handles EBADF gracefully by removing the offending fds. |
| 53 | |
58 | |
| 54 | whats missing? |
59 | whats missing? |
| 55 | |
60 | |
| 56 | - evdns, evhttp, bufferevent are missing, libev is only an even library at |
61 | - evdns, evhttp, bufferevent are missing, libev is only an even library at |
| 57 | the moment. |
62 | the moment. |
| 58 | |
63 | |
| 59 | - no priority support at the moment. |
64 | - no priority support at the moment |
| 60 | |
65 | |
| 61 | - kqueue, poll (libev currently implements epoll and select). |
66 | - kqueue, poll (libev currently implements epoll and select) |
| 62 | |
67 | |
|
|
68 | - windows support (whats windows?) |
|
|
69 | |
