The bufferevent interface also has multiple backends, so that it can take advantage of systems that provide faster ways to do nonblocking IO, such as the Windows IOCP API.
分类: LINUX
2011-05-23 20:05:59
The bufferevent interface also has multiple backends, so that it can take advantage of systems that provide faster ways to do nonblocking IO, such as the Windows IOCP API.
This module implements the buffers underlying bufferevents, and provides functions for efficient and/or convenient access.
A simple HTTP client/server implementation.
A simple DNS client/server implementation.
A simple RPC implementation
When Libevent is built, by default it installs the following libraries:
All core event and buffer functionality. This library contains all the event_base, evbuffer, bufferevent, and utility functions.
This library defines protocol-specific functionality that you may or may not want for your application, including HTTP, DNS, and RPC.
This library exists for historical reasons; it contains the contents of both libevent_core and libevent_extra. You shouldn’t use it; it may go away in a future version of Libevent.
The following libraries are installed only on some platforms:
This library adds threading and locking implementations based on the pthreads portable threading library. It is separated from libevent_core so that you don’t need to link against pthreads to use Libevent unless you are actually using Libevent in a multithreaded way.
This library provides support for encrypted communications using bufferevents and the OpenSSL library. It is separated from libevent_core so that you don’t need to link against OpenSSL to use Libevent unless you are actually using encrypted connections.