On Tue, Feb 8, 2011 at 6:45 PM, Ivan Novick wrote:
> On Tue, Feb 8, 2011 at 11:08 AM, Nick Mathewson wrote:
>> On Mon, Feb 7, 2011 at 5:15 PM, Ivan Novick wrote:
>>> Hello,
>>>
>>> I am testing fault tolerance in my application that is written using
>>> libevent-1.4.6
>>
>> I'd seriously suggest
On Tue, Feb 8, 2011 at 11:08 AM, Nick Mathewson wrote:
> On Mon, Feb 7, 2011 at 5:15 PM, Ivan Novick wrote:
>> Hello,
>>
>> I am testing fault tolerance in my application that is written using
>> libevent-1.4.6
>
> I'd seriously suggest that you always use the latest stable release,
> or at the v
On Feb 8, 2011, at 8:08 PM, Nick Mathewson wrote:
>> Do you know how I can detect the disconnection caused by bringing down
>> the interface on the server ... while still using libevent?
>
> If there's a good way to do this, Libevent or no, I'd like to know about it
> too.
The best reliable wa
On Tue, Feb 08, 2011 at 02:08:39PM -0500, Nick Mathewson wrote:
> On Mon, Feb 7, 2011 at 5:15 PM, Ivan Novick wrote:
> > Do you know how I can detect the disconnection caused by bringing down
> > the interface on the server ... while still using libevent?
>
> If there's a good way to do this, Li
On Mon, Feb 7, 2011 at 5:15 PM, Ivan Novick wrote:
> Hello,
>
> I am testing fault tolerance in my application that is written using
> libevent-1.4.6
I'd seriously suggest that you always use the latest stable release,
or at the very least the most recent stable release in the 1.4.x
series. Ther
Hello,
I am testing fault tolerance in my application that is written using
libevent-1.4.6
The application has a client and server connecting over TCP
and the event is setup like this on the client:
event_set(event, sock, EV_READ | EV_PERSIST, recv_from_server, h);
Then I login to the server a
