<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 14, 2011, at 4:05 AM, Laurens Van Houtven 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-align: -webkit-auto; 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; "><blockquote class="gmail_quote" style="margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; ">At least in Twisted, transports and protocols do not exist in a vacuum;<br>they have to be hooked up via the reactor. Will this PEP define<br>a (skeletal) API to be implemented by potential reactors, or is that<br>going to left entirely unspecified, like WSGI?<br></blockquote><div><br>Entirely unspecified, because different implementations have to do pretty different things.<br></div></span></blockquote><br></div><div>I thought the idea was to include an asyncore reactor interface? My assumption was that we'd provide an adapter around the Twisted reactor which would provide some basic functionality, like listenTCP, connectTCP, and callLater.</div><div><br></div><div>-glyph</div></body></html>