<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 15, 2011, at 4:08 PM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; "><blockquote type="cite">However, I should note that with the advent of endpoints, ClientFactory<span class="Apple-converted-space"> </span><br></blockquote><blockquote type="cite">is no longer necessary. Connection failure is communicated on an<span class="Apple-converted-space"> </span><br></blockquote><blockquote type="cite">endpoint via the Deferred from connect() errbacking, so there's no need<span class="Apple-converted-space"> </span><br></blockquote><blockquote type="cite">for the extra callbacks that ClientFactory provides.<br></blockquote><br>Except clientConnectionLost.<br></span></span></blockquote></div><div><br></div><div>I chose my words carefully :-).</div><br><div>clientConnectionLost was always a duplicate of IProtocol.connectionLost.</div><div><br></div><div>It might be <i>handy</i> to have that notification delivered in multiple places (specifically, for implementing ReconnectingClientFactory), but it's not <i>necessary</i> (there's no "need" for it) since you can clone it by wrapping IProtocol instead of duplicating it in the guts of the reactor.</div><div><br></div><div>-glyph</div><div><br></div></body></html>