… | |
… | |
9 | break the other) |
9 | break the other) |
10 | |
10 | |
11 | - fork() is supported and can be handled |
11 | - fork() is supported and can be handled |
12 | (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) |
13 | |
13 | |
14 | - timers are handled as a priority queue |
14 | - timers are handled as a priority queue (important operations are O(1)) |
15 | (libevent uses a less efficient red-black tree) |
15 | (libevent uses a much less efficient but more complex red-black tree) |
16 | |
16 | |
17 | - supports absolute (wallclock-based) timers in addition to relative ones, |
17 | - 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. |
18 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
19 | |
19 | |
20 | - timers can be repeating (both absolute and relative ones) |
20 | - timers can be repeating (both absolute and relative ones) |
… | |
… | |
52 | |
52 | |
53 | - simpler design, backends are potentially much simpler |
53 | - simpler design, backends are potentially much simpler |
54 | (in libevent, backends have to deal with watchers, thus the problems) |
54 | (in libevent, backends have to deal with watchers, thus the problems) |
55 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) |
55 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) |
56 | |
56 | |
|
|
57 | - libev handles EBADF gracefully by removing the offending fds. |
|
|
58 | |
57 | whats missing? |
59 | whats missing? |
58 | |
60 | |
59 | - 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 |
60 | the moment. |
62 | the moment. |
61 | |
63 | |