On 10.09.2012 18:32, Joachim Bauch wrote:
> On 10.09.2012 16:51, Nick Mathewson wrote:
[...]
>> I'd like a better distinction between functions that should be called
>> by the implementation, and functions that exist to be called by the
>> users of this type. Right now I am pretty sure which are w
On 10.09.2012 16:51, Nick Mathewson wrote:
> Having new *connect_hostname commands is making me think that maybe
> this should be an abstract method of bufferevent that only some
> bufferevent subtypes support.
Yes, the whole "lookup-and-start-connecting" part should be refactored
to a common meth
On Thu, Sep 6, 2012 at 5:30 PM, Joachim Bauch wrote:
> -Ursprüngliche Nachricht-
> Von:Nick Mathewson
> [...]
>> Sounds like a big but fun project. You might want to look at
>> bufferevent_sock.c first; bufferevent_openssl.c has to jump through a
>> lot of annoying hoops because the
On 08.09.2012 00:03, Mark Ellzey wrote:
> On Thu, Sep 06, 2012 at 11:30:54PM +0200, Joachim Bauch wrote:
>> Thanks for the heads up. The socket-based code surely will be helpful
>> when the implementation starts. I wrote an initial draft of how the
>> API could look like and put it on github:
>>
On Thu, Sep 06, 2012 at 11:30:54PM +0200, Joachim Bauch wrote:
> Thanks for the heads up. The socket-based code surely will be helpful
> when the implementation starts. I wrote an initial draft of how the
> API could look like and put it on github:
> https://github.com/fancycode/Libevent/blob/buf
On Wed, Sep 5, 2012 at 5:14 AM, Joachim Bauch wrote:
> Hi,
>
> I'm looking for a way to implement a bufferevent that uses a custom API
> to read/write data to the network - similar to what the SSL bufferevent
> does with the OpenSSL BIO.
>
> Any hints on what would be the best way to implement thi
