On 1/30/07, Wouter Wijngaards <[EMAIL PROTECTED]> wrote:
Please, why put these really big http and dns protocols into an event
handling library? I would prefer libevent to stay focused on providing
portable select() and alternatives wrappers.
The http and evdns are pretty big compared to the rest of libevent. They
can be put in their own library(or -ies) perhaps? Some sort of
libevent-driven application support?
There has been some talk about libevent creating two different
libraries during compile. One would be the traditional libevent and
the other one would layer on top of it. Still thinking about the
best way of doing this, but you are not the only one with concerns
about bloat.
Niels.
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
