[Python-ideas] PEP 3156: Clarifying the different components of the event loop API

Sun Jan 20 14:18:10 CET 2013

On 2013年1月20日 23:10:56 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Jan 20, 2013 10:46 PM, "Antoine Pitrou" <solipsis-xNDA5Wrcr86sTnJN9+BGXg at public.gmane.org> wrote:
> >
> > On 2013年1月20日 12:34:24 +1000
> > Nick Coghlan <ncoghlan at gmail.com> wrote:
> > >
> > > Low level transport creation:
> > > - create_connection()
> > > - create_pipe() # Once it exists in the PEP
> >
> > You need some kind of create_listener() too.
>> That's actually the "start_serving" method up in the event monitoring
> section. While it does end up creating transports, the overall flow is
> rather different from the client side one.

Ah, right. Well, in any case, the API is much too limited. It doesn't
support SSL, and it doesn't support UDP.
“TBD: Support SSL? I don't even know how to do that synchronously, and
I suppose it needs a certificate.”
See http://docs.python.org/dev/library/ssl.html#server-side-operation
(and the non-blocking handshake part also applies)
Regards
Antoine.