I got it. Thanks a lot for clarification. :-)
DJ
On Wed, Jun 1, 2011 at 8:50 PM, Nick Mathewson wrote:
> On Tue, May 31, 2011 at 1:40 PM, deepak jain
> wrote:
> > Hi Nick,
> > Thanks a lot for your reply.
> > One more doubt about bufferevent.
> > As in socket networking programming, Sometimes
On Tue, May 31, 2011 at 1:40 PM, deepak jain wrote:
> Hi Nick,
> Thanks a lot for your reply.
> One more doubt about bufferevent.
> As in socket networking programming, Sometimes It may require more than one
> read/recv in server side for a single write by a client, depending upon
> server socket'
Hi Nick,
Thanks a lot for your reply.
One more doubt about bufferevent.
As in socket networking programming, Sometimes It may require more than one
read/recv in server side for a single write by a client, depending upon
server socket's read buffer availability. Similarly here our read callback
ma
On Mon, May 30, 2011 at 5:03 AM, deepak jain wrote:
> Hello,
> I am a new user of libevent and new to asynchronous I/O , so the question
> may seem quite naive.
> I am building an application based on libevent on linux using epoll backend.
> Sometime clients of my application can write a huge dat
Hello,
I am a new user of libevent and new to asynchronous I/O , so the question
may seem quite naive.
I am building an application based on libevent on linux using epoll backend.
Sometime clients of my application can write a huge data to my application
say 100K bytes.
I am using buffer_read_bu
