<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 1:03 PM, Orestis Markou 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; ">But, for most of the one-shot cases it seems that a ClientCreator (or an endpoint) would serve the same purpose, no?<br></span></span></blockquote></div><br><div>I am not sure that I understand your message. ClientFactory will be re-used if you re-use it; it won't be re-used if you don't. There's no particularly compelling reason to do so or not to do so; just whatever happens to make sense within your application.</div><div><br></div><div>However, I should note that with the advent of endpoints, ClientFactory is no longer necessary. Connection failure is communicated on an endpoint via the Deferred from connect() errbacking, so there's no need for the extra callbacks that ClientFactory provides.</div><div><br></div><div>-glyph</div><div><br></div></body></html>