On Wed, May 11, 2011 at 2:05 AM, Kun Xi wrote:
> 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
On Wed, May 11, 2011 at 11:21 AM, Scott Lamb wrote:
> On Wed, May 11, 2011 at 10:12 AM, Cliff Frey wrote:
>> I spent some more time thinking about this, and I have a few use cases that
>> it might be worth keeping in mind.
>>
>> It would be nice if the API made it easy to hook up a received HTTP
On Wed, May 11, 2011 at 10:12 AM, Cliff Frey wrote:
> I spent some more time thinking about this, and I have a few use cases that
> it might be worth keeping in mind.
>
> It would be nice if the API made it easy to hook up a received HTTP request
> (where we are the server) to an outgoing HTTP req
I spent some more time thinking about this, and I have a few use cases that
it might be worth keeping in mind.
It would be nice if the API made it easy to hook up a received HTTP request
(where we are the server) to an outgoing HTTP request (where we are the
client) in order to make building an HT
On Wed, May 11, 2011 at 04:20:33AM -0700, Scott Lamb wrote:
> It's libevent's doom, too: the extra code for spooling is a
> maintenance burden. I don't like options C or D.
>
I am officially out of this thread. This back and forth has obviously
derailed with reasons-why-not instead of how-about-w
On Tue, May 10, 2011 at 9:11 PM, Mark Ellzey wrote:
> 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_chu
