This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients gvanrossum, pitrou, vstinner, yselivanov
Date 2015-01-27.22:47:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwb4bZa83p+M3ki__G8S1uhDB4Kpvhiasvm=oiE3qg6TTg@mail.gmail.com>
In-reply-to <1422398476.1.0.327291922935.issue23333@psf.upfronthosting.co.za>
Content
FYI I opened a thread about this issue on the Tulip mailing list.

Antoine Pitrou added the comment:
> IMO, connection_lost() should never be called if connection_made() wasn't called. That's a breach of the API contract.

Yes, I agree.

> (at one point, I suggested a connection_failed() for that purpose, but it was shut down - it was in relationship to the idea of a reconnecting client, but can still be more broadly useful)

I like the "connection_failed" name. We may call
protocol.connection_failed(transport), so the protocol gets access to
the socket and so to the IP addres.
History
Date User Action Args
2015-01-27 22:47:06vstinnersetrecipients: + vstinner, gvanrossum, pitrou, yselivanov
2015-01-27 22:47:06vstinnerlinkissue23333 messages
2015-01-27 22:47:06vstinnercreate