On Wed, Oct 18, 2006 at 12:11:20PM -0700, Scott Lamb wrote: > On Oct 18, 2006, at 11:49 AM, William Ahern wrote: > >On Wed, Oct 18, 2006 at 12:04:11AM -0600, Jason Ish wrote: > >>I ran across at least one criticism of libevent gaining too much > >>other > >>than pure event library: > >>http://varnish.projects.linpro.no/wiki/EventLibrary > >> > > > >All of these criticisms are partially or wholly invalid. > > > >The DNS and HTTP code is effectively only distributed in the > >tarball; it's > >not part of the library itself. > > Presumably they _will_ be in the library, but I don't see the > problem, either. I'm using libevent in a resource-constrained system, > and typing "p4 delete foo.c" didn't take much of my time. (By the > way, Niels, if you at some point get a 2wire iNID, look for your name > in the user manual. :) On a less-constrained system, you can simply > not use those parts of the library.
I've simply wrapped many of the libevent functions to take an event_base as the first parameter. Well, its not really an event base, but my wrapper around one. Then I don't have to worry about setting the base, and more importantly, the people who I have to write code with don't have to worry about it. My original post was not really to bring up the misfeatures that are brought up in the wiki post, but more to query about more 'framework' type features being incorporated into libevent. Albeit a little application specific, I've built up many 'framework' type things around libevent that more or less match a lot of the features found in Twisted (www.twistedmatrix.com) and I find these very useful, but I don't know if they belong in libevent. -- Jason _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users