On Mon, May 23, 2011 at 8:55 AM, Mark Ellzey wrote:
> I have been reconsidering the idea of actually putting this into
> Libevent itself, mostly because I have intentions to abstract a lot of
> the duties a real http server would do: thread pooling, AIO spooling,
> RESTfull type configuration, and
On Wed, May 25, 2011 at 11:11:49PM +0200, Aleksandar Lazic wrote:
> Dear Mark,
>
> What do you think about to use the mongrel2 parser?
>
> https://github.com/zedshaw/mongrel2
>
> => mongrel2/src/http11
The general arch seems to be completely derived from ry (backend structs
look pretty much the
Dear Mark,
On Mon 23.05.2011 10:55, Mark Ellzey wrote:
I am the owner, but the ry/http-parser is MIT. But odd thing is - it is a direct
copy from NGINX parser; 2 Clause BSD, but re-licensed as MIT.
I asked him about the possibility of a license change but didn't seem
interested.
But it seems
On Mon, May 23, 2011 at 8:55 AM, Mark Ellzey wrote:
>> On Mon, May 16, 2011 at 10:30 PM, Mark Ellzey wrote:
>> Are you the copyright holder? If so, why not stick to BSD to keep
>> things simple.
>>
>> Kevin
>
> As an FYI, Libevent already does a good job of keeping track of all
> non-BSD specifi
> On Mon, May 16, 2011 at 10:30 PM, Mark Ellzey wrote:
> Are you the copyright holder? If so, why not stick to BSD to keep
> things simple.
>
> Kevin
As an FYI, Libevent already does a good job of keeping track of all
non-BSD specific code in their LICENCE file.
But..
I have been reconsiderin
On Mon, May 16, 2011 at 10:30 PM, Mark Ellzey wrote:
> Since libevhtp uses a MIT clause license, it is compatible with our
> current BSD license AFIAK. Would be nifty to see, once stable, if we
> can have this feature as an option in libevent.
Are you the copyright holder? If so, why not stick
On Sun, May 15, 2011 at 06:24:02PM +0800, lx wrote:
> i'll try to use it.
>
Thanks,
I just pushed a bunch of chances including a few more hook mechanisms. A
more refined 1.0 vs 1.1 compatability set. Some initial perf testing
with httperf comparing test.c (from libevhtp) and http_bench (from
l
i'll try to use it.
2011/5/15 Mark Ellzey
> I have created a new project called libevhtp, a server-only replacement
> for the current libevent http API. The API utilizes a streaming http
> parser, which allows me to hook into a lot of places.
>
> You can treat the API just like you would normal
I have created a new project called libevhtp, a server-only replacement
for the current libevent http API. The API utilizes a streaming http
parser, which allows me to hook into a lot of places.
You can treat the API just like you would normal evhttp_* calls, but
instead use evhtp_*.
The flexibil
