Re: [Libevent-users] detected a bad network connection for a TCP connection

[Nick Mathewson <nickm@xxxxxxxxxxxxx>]

On Tue, Feb 8, 2011 at 6:45 PM, Ivan Novick <novickivan@xxxxxxxxx> wrote:
> On Tue, Feb 8, 2011 at 11:08 AM, Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote:
>> On Mon, Feb 7, 2011 at 5:15 PM, Ivan Novick <novickivan@xxxxxxxxx> 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.  There have been a lot of bugs fixed since 1.4.6-stable.  (Not
>> that this affects your question here, but
>
> Point taken.  We do have a QA cycle to make such a change ... but i am
> going to make a point of getting this upgraded.
>
> I assume you recommend the latest and greatest version

The latest version is 2.0.10-stable; the latest in the 1.4 series is
1.4.14b-stable.  Either should fix a number of bugs.

>.  Can we expect
> the same behavior in general or have the intended semantics of the API
> changed subtley between 1.4.6 and the latest and greatest version?

If you're worried about incompatibilities, you could stick with
1.4.14b for now.  All code written correctly to work with 1.4.x should
also work with 2.0.x, but in some cases people have found issues with
incorrect code.  We tried to be as bug-compatible as possible, except
when the bugs in question were downright egregious.

See the ChangeLog files in the respective releases for a list of
changes since 1.4.6-stable; see the "whatsnew-2.0.txt" document in the
2.0.10-stable distribution for more info on changes in 2.0.x

To the best of my knowledge, neither of these releases changes the
behavior of sockets open on an interface that gets taken down, but
they fix lots of other bugs, some of which you might care about.

hth,
-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.