<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 6, 2010, at 4:18 PM, Christopher Armstrong wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-size: medium; 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; "><span class="Apple-style-span" style="font-family: monospace; ">We don't want to have any more transport-specific methods on the<br>reactor, and this has nothing to do with ZMQ. We also don't want to<br>have connectSOCKS, or listenSerialPort. Fortunately, the endpoints<br>API[1] was very recently merged to Twisted trunk, so any new<br>transport-specific connectors/listeners can be implemented in terms of<br>its interfaces. listenTCP and so forth should eventually be deprecated<br>in preference to the endpoints APIs.<br></span></span></blockquote></div><br><div>While the endpoints APIs are great and everyone should use them, I think it's putting it a bit strongly to say that listenTCP and friends will be deprecated. Reactors are still pluggable, and we'll need a mechanism for endpoints and reactors to communicate. There may be some evolution of those APIs in the long term (in particular, the way that connectTCP interacts with client factories is slightly weird) but I think that there will always be something lower-level than endpoints that is still a public, supported API.</div><div><br></div><div>You just won't be encouraged to use that API at the *application* layer, because endpoints are more flexible.</div><div><br></div></body></html>