Re: [Libevent-users] accessing a bufferevent's evbuffer directly

2009-04-08 Thread Ka-Hing Cheung
On Mon, 2009-04-06 at 11:17 -0700, Nick Mathewson wrote: If you want to try 0-copy stuff with bufferevents, you'll need to wait for Libevent 2.0. Libevent 1.4 doesn't really support that so well. Is there some kind of rough schedule on when libevent 2.0 may come out? -khc

Re: [Libevent-users] accessing a bufferevent's evbuffer directly

2009-04-08 Thread Nick Mathewson
On Wed, Apr 08, 2009 at 11:06:37AM -0700, Ka-Hing Cheung wrote: On Mon, 2009-04-06 at 11:17 -0700, Nick Mathewson wrote: If you want to try 0-copy stuff with bufferevents, you'll need to wait for Libevent 2.0. Libevent 1.4 doesn't really support that so well. Is there some kind of rough

Re: [Libevent-users] libevent SSL support

2009-04-08 Thread Dan Kegel
On Wed, Apr 8, 2009 at 9:53 AM, Suresh Pachiappan suresh...@hotmail.com wrote: I am looking for SSL support in libevent. I don't know how interesting it is, but Chromium uses both libevent and SSL. On Linux, it uses NSS to provide SSL; on Mac, it uses the native Mac SSL library. You can see

[Libevent-users] Parsing request uri

2009-04-08 Thread Rauan Maemirov
Hey guys. I'm new to C, and couldn't find any docs on how to parse query_string with evhttp_parse_query. Interested in parsing it to kind of associative array. ___ Libevent-users mailing list Libevent-users@monkey.org

RE: Was: Re: [Libevent-users] libevent SSL support

2009-04-08 Thread Suresh Pachiappan
Thanks a lot, Rocco Dan. The libevent ssl patches is a lot more than I asked for! -suresh. Date: Wed, 8 Apr 2009 23:32:13 +0200 From: ro...@tecsiel.it To: suresh...@hotmail.com CC: d...@kegel.com; libevent-users@monkey.org Subject: Was: Re: [Libevent-users] libevent SSL support On 8

[Libevent-users] function delegates

2009-04-08 Thread William Ahern
Attached is a crack at supporting type-independent callback handlers. I've gotten tired of stubbing out handlers everywhere. It uses libffi (distributed with GCC), and GCC's type introspection builtins. Strictly speaking, it'll never be portable; but in practice it should be quite portable, at