>
> So I like the idea of getting read-by-read notification of data as it
> arrives. I'm not thrilled with the idea of changing default behavior
> wrt what counts as a read, though. Either a flag or another kind of
> callback would make me much more comfortable about the change here.
I will try
Hello,
I am a new user of libevent, so the question may seem quite naive.
I am building an application based on libevent-2.10 on linux using the
epoll backend. The application maintains BST using tsearch, tdelete
for access control. The tree is built from the command line argument,
and looked up
I just whipped up a quick bare-bones http server using only bufferevents
and a MIT licensed http parser (which if I am not mistaken - is
compatible with bsd).
https://github.com/ellzey/bufferevent_http_parser/blob/master/evhttp.c
This is the type of control I would look for in a http request pro
On Tue, May 10, 2011 at 04:04:27PM -0700, Scott Lamb wrote:
> I don't see the point in libevent implementing spooling to a file
> (descriptor). If an application wants that, it can implement it on top
> of the existing evhttp_request_set_chunked_cb + the fairly small
> patches being proposed (call
On Tue, May 10, 2011 at 04:14:42PM -0700, Scott Lamb wrote:
> It occurs to me by "install a handler for" you might be meaning a
> custom filesystem via kernel module or FUSE or something. I don't like
> that either;
I never said nor implied such a thing.
**
On Tue, May 10, 2011 at 4:04 PM, Scott Lamb wrote:
> On Tue, May 10, 2011 at 4:46 AM, Mark Ellzey wrote:
>> On Tue, May 10, 2011 at 09:04:42AM +0200, Roman Puls wrote:
>>> whilst this might be nice for flow-blown web services, this does not
>>> work for embedded systems that have no or very limit
On Tue, May 10, 2011 at 4:46 AM, Mark Ellzey wrote:
> On Tue, May 10, 2011 at 09:04:42AM +0200, Roman Puls wrote:
>> whilst this might be nice for flow-blown web services, this does not
>> work for embedded systems that have no or very limited disk storage.
>>
>> Also, this pattern disables effect
This looks awesome. Is it possible to add a regression test that triggers
the behavior?
On Mon, May 9, 2011 at 11:46 PM, Kevin Ko wrote:
> Hi,
>
> Patch in question:
> -
> Fix the case when failed evhttp_make_request() leaved request in the queue.
> -
> http://levent.git.sourceforge.net/git/g
On Tue, May 10, 2011 at 09:04:42AM +0200, Roman Puls wrote:
> whilst this might be nice for flow-blown web services, this does not
> work for embedded systems that have no or very limited disk storage.
>
> Also, this pattern disables effective stream handling, e.g. where
> you don't want to store
On May 07.05.2011 20:26, Mark Ellzey wrote:
On Sat, May 07, 2011 at 01:07:40AM -0400, Nick Mathewson wrote:
*lots of text here*
One of the ways nginx deals with very large streams of data is to
actually spool the data to file. By default this is turned off. But
this may be a simple solution to
10 matches
Mail list logo
