| … | |
… | |
| 16 | Some of the specialties of libev not commonly found elsewhere are: |
16 | Some of the specialties of libev not commonly found elsewhere are: |
| 17 | |
17 | |
| 18 | - extensive and detailed, readable documentation (not doxygen garbage). |
18 | - extensive and detailed, readable documentation (not doxygen garbage). |
| 19 | - fully supports fork, can detect fork in various ways and automatically |
19 | - fully supports fork, can detect fork in various ways and automatically |
| 20 | re-arms kernel mechanisms that do not support fork. |
20 | re-arms kernel mechanisms that do not support fork. |
| 21 | - highly optimised select, poll, epoll, kqueue and event ports backends. |
21 | - highly optimised select, poll, linux epoll, linux aio, bsd kqueue |
|
|
22 | and solaris event ports backends. |
| 22 | - filesystem object (path) watching (with optional linux inotify support). |
23 | - filesystem object (path) watching (with optional linux inotify support). |
| 23 | - wallclock-based times (using absolute time, cron-like). |
24 | - wallclock-based times (using absolute time, cron-like). |
| 24 | - relative timers/timeouts (handle time jumps). |
25 | - relative timers/timeouts (handle time jumps). |
| 25 | - fast intra-thread communication between multiple |
26 | - fast intra-thread communication between multiple |
| 26 | event loops (with optional fast linux eventfd backend). |
27 | event loops (with optional fast linux eventfd backend). |
| 27 | - extremely easy to embed. |
28 | - extremely easy to embed (fully documented, no dependencies, |
|
|
29 | autoconf supported but optional). |
| 28 | - very small codebase, no bloated library. |
30 | - very small codebase, no bloated library, simple code. |
| 29 | - fully extensible by being able to plug into the event loop, |
31 | - fully extensible by being able to plug into the event loop, |
| 30 | integrate other event loops, integrate other event loop users. |
32 | integrate other event loops, integrate other event loop users. |
| 31 | - very little memory use (small watchers, small event loop data). |
33 | - very little memory use (small watchers, small event loop data). |
| 32 | - optional C++ interface allowing method and function callbacks |
34 | - optional C++ interface allowing method and function callbacks |
| 33 | at no extra memory or runtime overhead. |
35 | at no extra memory or runtime overhead. |
| 34 | - optional Perl interface with similar characteristics (capable |
36 | - optional Perl interface with similar characteristics (capable |
| 35 | of running Glib/Gtk2 on libev, interfaces with Net::SNMP and |
37 | of running Glib/Gtk2 on libev). |
| 36 | libadns). |
|
|
| 37 | - support for other languages (multiple C++ interfaces, D, Ruby, |
38 | - support for other languages (multiple C++ interfaces, D, Ruby, |
| 38 | Python) available from third-parties. |
39 | Python) available from third-parties. |
| 39 | |
40 | |
| 40 | Examples of programs that embed libev: the EV perl module, |
41 | Examples of programs that embed libev: the EV perl module, node.js, |
| 41 | rxvt-unicode, gvpe (GNU Virtual Private Ethernet), the Deliantra MMORPG |
42 | auditd, rxvt-unicode, gvpe (GNU Virtual Private Ethernet), the |
| 42 | server (http://www.deliantra.net/), Rubinius (a next-generation Ruby |
43 | Deliantra MMORPG server (http://www.deliantra.net/), Rubinius (a |
| 43 | VM), the Ebb web server, the Rev event toolkit. |
44 | next-generation Ruby VM), the Ebb web server, the Rev event toolkit. |
| 44 | |
45 | |
| 45 | |
46 | |
| 46 | CONTRIBUTORS |
47 | CONTRIBUTORS |
| 47 | |
48 | |
| 48 | libev was written and designed by Marc Lehmann and Emanuele Giaquinta. |
49 | libev was written and designed by Marc Lehmann and Emanuele Giaquinta. |
