On Sun, Oct 21, 2007 at 02:00:38PM +0200, Chris Brody-GMail wrote: [...] > Thank you guys for the attention to the issue. Small questions: 1. > would the evbuffer & bufferevents still be part of the libevent-core, > or something else? I am working on a C++ interface for this part.
I'm pretty sure that evbuffer and friends should stay in event-core,
for two reasons:
* Unlike HTTP, RPC, and DNS, they're pretty protocol-neutral.
* Like event_base, they can be optimized on different platforms in
different ways. (Windows, for instance, is begging for an IOCP
implementation of bufferevents. I've got one from a student that
I want to merge into the next major revision or the one after
that, time permitting.)
> 2. Could we give "extras" a slightly sexier name such as WWW or
> web-server? I do find this to be a valuable part as well, and I am
> planning to work on a C++ interface for the HTTP server part in the
> future.
It's not www only: it's http, dns, and rpc. In the future, it might
grow.
I'm going to go with the name Niels gave, since it lets me make the
changes sooner rather than later. :)
yrs,
--
Nick Mathewson
pgp2u2EZmxbhH.pgp
Description: PGP signature
_______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
