Libevent–an Event Notification Library
The libevent API (libevent application) provides a mechanism (mechanism) to execute (execute) a callback function (callback function) when a specific ( Special) event occurs on (occurs in) a file descriptor (file descriptor) or after a timeout have been reached. (After time expires)
Furthermore (also), Libevent also support callbacks due to (for) signals (signal) or regular timeouts. (Regular time-outs)
libevent is meant to (for) Replace the event loop (time loop) found in (distributed) event driven network servers (event-driven networking server). An application just needs to call Event_dispatch ()and then (then) Add or remove events dynamically (dynamically) without Havi Ng to (not required) change the event loop.
currently, libevent supports /dev/poll , kqueue (2) , Event ports , posix Select (2) , windows Select () , Poll (2) , and epoll (4) . The internal event mechanism (internal events mechanism) is completely independent of the exposed (exposed) event API, and a simple update of libe Vent can provide new functionality (function) without have to redesign (re-engineered) the applications. As a result, Libevent allows for (allow) portable application (green software) development and provides the most scal Able (extensible) event notification mechanism available on an operating system. Libevent can also is used for is used for multi-threaded multithreading applications, either (also) by (via) isolating (isolated) each event_base (event library) so th At (for convenience) only a single thread accesses (accessed) it, or by locked (locked) access to a single shared event_base. Libevent should Compile (compilation) on Linux, *bsd, Mac OS X, Solaris, Windows, and more.
Libevent additionally (incidental) provides a sophisticated (complex) framework (framework) for buffered (buffered) network IO with the support for Sockets (set interface), Filters (filter), rate-limiting (speed limit), SSL (Secure Sockets Layer), Zero-copy file transmission (0 Copy file transfer), and IOCP input and output applications. Libevent includes support for several useful protocols (protocol), including DNS, HTTP, and a minimal (minimally) RPC (Remote Procedure Call) framework ( Framework).
More information about event notification mechanisms for network servers can is found on (based on) Dan Kegel ' s "the c10k problem "Web page.
A Mailing list for libevent (libevent mailing list) is now available. Libevent is maintained (maintained) by Nick Mathewson and Niels Provos.
See the English words that Libevent met