Thanks Azat! Seems libevhtp is preferred over libevent's http.
Will check out libevhtp.
>> I don't think that libevent *support* pipelining (a quick look at
bufferevent_{enable,disable}() at http.c).
>> As for stability of pipe lining it depends from implementations I guess.
You mean application design? I thought pipelining will be handled by
library and
request callback triggered in application.
Thanks,
Kaustubh
On Tue, Jun 23, 2015 at 4:37 PM, Azat Khuzhin <[email protected]> wrote:
> On Tue, Jun 23, 2015 at 04:04:41PM +0530, Kaustubh Deorukhkar wrote:
> > Hello,
> >
> > I am new to libevent and would like to know how is the support for HTTP
> > protocol. I am evaluating it for a http server and would help if you all
> > can share experience with using libevent HTTP in prod.
>
> Hi,
>
> Well, libevent already have http server implementation, and also there
> is libevhtp.
>
> > - Does it support full HTTP/1.1 ?
>
> I don't sure about *full*, but it supports
> - Host:
> - Transfer-Encoding:chunked
> - 100 Continue
> - Some thing that I forgot to mention
>
> > - HTTP pipe-lining (found some posts about issues with pipe-lining on
> keep
> > alive, is it fixed and stable?)
>
> I don't think that libevent *support* pipelining (a quick look at
> bufferevent_{enable,disable}() at http.c).
> As for stability of pipe lining it depends from implementations I guess.
>
> > Will be very helpful if someone can share or point me to docs if any?
>
> http://www.wangafu.net/~nickm/libevent-book/
> http://libevent.org
> ***********************************************************************
> To unsubscribe, send an e-mail to [email protected] with
> unsubscribe libevent-users in the body.
>
