Re: [Libevent-users] EV_WRITE - Wait for a socket or FD to become writeable.

On Sep 3, 2012, at 8:13 PM, Parvez Shaikh wrote: Purpose of doing this is to make only one thread access socket descriptor. I have to use multiple threads(thread pool that does some mundane processing of messages) for utilizing multiple cores as much as possible(each thread access no sha

Re: [Libevent-users] EV_WRITE - Wait for a socket or FD to become writeable.

Hi Nir, Purpose of doing this is to make only one thread access socket descriptor. I have to use multiple threads(thread pool that does some mundane processing of messages) for utilizing multiple cores as much as possible(each thread access no shared resource except queuing message for send); als

Re: [Libevent-users] EV_WRITE - Wait for a socket or FD to become writeable.

On Mon, Sep 3, 2012 at 1:05 PM, Parvez Shaikh wrote: > Thanks Oleg and Nir. > > I am also pursuing another approach. Here I have defined a custom event > (associated with FD but not having either EV_READ or EV_WRITE) and there is > no time out either. > > A thread queues data to "outgoing message

Re: [Libevent-users] EV_WRITE - Wait for a socket or FD to become writeable.

Thanks Oleg and Nir. I am also pursuing another approach. Here I have defined a custom event (associated with FD but not having either EV_READ or EV_WRITE) and there is no time out either. A thread queues data to "outgoing message list" and activates an event. In response to this, event reactor t