Larry, On 10/2/07, Larry Lewis <[EMAIL PROTECTED]> wrote: > > The approach I've seen most often is to mark functions as deprecated and > wait for a major release with expected API breakages to actually remove > them. I doubt the inclusion of http and dns will be a deal-breaker for > anyone, but if this is a sign of more and more code built on top of libevent > to be included in the core library, it may discourage porting and usage. >
Y are bringing a good point.. libevent is a great library for events demultiplexing, and I like it a lot. I would also doubt the addition of HTTP and DNS client stacks to the library itself, whereas they can be very good as the examples and testing applications. libcurl has developed a good API for its integration with libevent. libcurl project also maintains and develops a very good asynchronous DNS client library, called c-ares (a clone of ares). Could it be a better path to concentrate the community efforts on integration of c-ares and libcurl with libevent and to assist better to applications? For example, curl-loader is using libevent for demultiplexing and HTTP and FTP client stacks of libcurl to create a client side HTTP/HTTPS/FTP/FTPS testing framework (disclaimer - I am a maintainer of curl-loader, and, therefore, biased). Sincerely, Robert Iakobashvili, coroberti %x40 gmail %x2e com ........................................................... http://curl-loader.sourceforge.net A web testing and traffic generation tool.
_______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users