Hi Nick,
On Thu, Nov 8, 2012 at 9:55 AM, Nick Mathewson wrote:
>
> Hello again!
>
> On Tue, Nov 6, 2012 at 4:12 PM, Himanshu S wrote:
>>
>> On Tue, Nov 6, 2012 at 7:37 AM, Nick Mathewson wrote:
>>
>
>> Right now the best way to do what you have in mind is to consider *why*
>>> you only want to
Hello again!
On Tue, Nov 6, 2012 at 4:12 PM, Himanshu S wrote:
>
> On Tue, Nov 6, 2012 at 7:37 AM, Nick Mathewson wrote:
>
> Right now the best way to do what you have in mind is to consider *why*
>> you only want to read partial data and then read again after the next event
>> loop -- there's
On Tue, Nov 6, 2012 at 7:37 AM, Nick Mathewson wrote:
>
> On Tue, Nov 6, 2012 at 12:29 AM, Himanshu S wrote:
>
>> Hi,
>>I am using bufferevent_* APIs for my application to read/write data to
>> TCP stream. When the data arrives, the read callback happens, I want to
>> read partial data (at ti
On Tue, Nov 6, 2012 at 12:29 AM, Himanshu S wrote:
> Hi,
>I am using bufferevent_* APIs for my application to read/write data to
> TCP stream. When the data arrives, the read callback happens, I want to
> read partial data (at times), and then be able to post an event back so
> that the event
Hi,
I am using bufferevent_* APIs for my application to read/write data to
TCP stream. When the data arrives, the read callback happens, I want to
read partial data (at times), and then be able to post an event back so
that the event is queued up and read callback is called again. I thought
even
