summaryrefslogtreecommitdiff
path: root/devel
diff options
context:
space:
mode:
authorpettai <pettai>2014-10-09 11:19:57 +0000
committerpettai <pettai>2014-10-09 11:19:57 +0000
commitedeb6e21b1b5074f7560a4573afa0669a606146f (patch)
tree8b3a924567d3256e8ee9989e3447efab19380b8a /devel
parentfee56c9a74de0668f11cc535efc92611bd5d573d (diff)
downloadpkgsrc-edeb6e21b1b5074f7560a4573afa0669a606146f.tar.gz
update to reflect current version
Diffstat (limited to 'devel')
-rw-r--r--devel/libevent/DESCR17
1 files changed, 11 insertions, 6 deletions
diff --git a/devel/libevent/DESCR b/devel/libevent/DESCR
index 40636d31a4c..1c24f631892 100644
--- a/devel/libevent/DESCR
+++ b/devel/libevent/DESCR
@@ -1,14 +1,19 @@
The libevent API provides a mechanism to execute a callback function when a
specific event occurs on a file descriptor or after a timeout has been
-reached.
+reached. Furthermore, libevent also support callbacks due to signals or
+ regular timeouts.
libevent is meant to replace the asynchronous event loop found in event
driven network servers. An application just needs to call event_dispatch()
and can then add or remove events dynamically without having to change the
event loop.
-Currently, libevent supports kqueue(2) and select(2). Support for poll(2)
-and /dev/poll is planned. The internal event mechanism is completely
-independent of the exposed event API, and a simple update of libevent can
-provide this new functionality without having to redesign the server
-applications.
+Currently, libevent supports /dev/poll, kqueue(2), event ports, select(2),
+poll(2), and epoll(4). The internal event mechanism is completely independent
+of the exposed event API, and a simple update of libevent can provide new
+functionality without having to redesign the applications.
+
+Libevent additionally provides a sophisticated framework for buffered network
+IO, with support for sockets, filters, rate-limiting, SSL, zero-copy file
+transmission, and IOCP. Libevent includes support for several useful protocols,
+including DNS, HTTP, and a minimal RPC framework.