* ->requeue support. An optimization of the AddTimer(0, ...) idiom
for immediately dispatching code at the next event loop iteration.
public-inbox uses this for fairly generating large responses
- iteratively (see PublicInbox::NNTP::long_response or git_async_cat
+ iteratively (see PublicInbox::NNTP::long_response or ibx_async_cat
for blob retrievals).
New features
which (if any) events it's interested in for the next loop iteration.
* Edge-triggering available via EPOLLET or EV_CLEAR. These reduce wakeups
- for unidirectional classes (e.g. PublicInbox::Listener sockets,
- and pipes via PublicInbox::HTTPD::Async).
+ for unidirectional classes when throughput is more important than fairness.
* IO::Socket::SSL support (for NNTPS, STARTTLS+NNTP, HTTPS)
-* dwaitpid (waitpid wrapper) support for reaping dead children
+* awaitpid (waitpid wrapper) support for reaping dead children
* reliable signal wakeups are supported via signalfd on Linux,
EVFILT_SIGNAL on *BSDs via IO::KQueue.