Re: [Twisted-Python] SSL4ClientEndpoint not updating the transport's connected flag on connection lost

> On Aug 11, 2016, at 06:59, Adi Roiban wrote: > > Hi, > > I have observed that when a SSL4ClientEndpoint was used, the > protocol's transport `connected` attribute is not updated by the > wrapper when the connection is lost. Hey Adi, I took a look through the code, and I think it's a lot sim

Re: [Twisted-Python] SSL4ClientEndpoint not updating the transport's connected flag on connection lost

On 20 August 2016 at 08:37, Glyph Lefkowitz wrote: > > On Aug 11, 2016, at 06:59, Adi Roiban wrote: > > Hi, > > I have observed that when a SSL4ClientEndpoint was used, the > protocol's transport `connected` attribute is not updated by the > wrapper when the connection is lost. > > > Hey Adi, > >

Re: [Twisted-Python] SSL4ClientEndpoint not updating the transport's connected flag on connection lost

> On Aug 20, 2016, at 2:13 AM, Adi Roiban wrote: > > On 20 August 2016 at 08:37, Glyph Lefkowitz > wrote: >> >> On Aug 11, 2016, at 06:59, Adi Roiban wrote: >> >> Hi, >> >> I have observed that when a SSL4ClientEndpoint was used, the >> protocol's transport `