[Security-sig] Unified TLS API for Python

[Cory Benfield]

> On 12 Jan 2017, at 10:14, Christian Heimes <christian at cheimes.de> wrote:
> 
> On 2017-01-12 09:45, Cory Benfield wrote:
>> 
>>> On 11 Jan 2017, at 21:23, Christian Heimes <christian at cheimes.de> wrote:
>>> 
>>> * Do we need to define blocking / non blocking state of the socket?
>> 
>> I think we want to support both. I’m not sure we need to expose it in the API: the implementation can check by asking the socket directly if it cares.
> 
> Do we need to support both? I thought that wrap_buffers() is the
> preferred way for non-blocking TLS with an event loop. You are the
> expert, do SChannel and SecureTransport work with non-blocking sockets
> and WantRead/WantWrite?

Preferred is a general truth, but not always specifically true. In particular, there is value in non-blocking sockets outwith an event loop.

Calling me “the expert” on this topic is a little strong, but I know that SecureTransport does.

Cory