[swift-server-dev] Next Server Security API Group Meeting
dev at xenonium.com
Mon Jan 30 01:45:49 CST 2017
> Le 29 janv. 2017 à 15:33, Helge Heß via swift-server-dev <swift-server-dev at swift.org> a écrit :
> a major thing the proposal is missing is a strong requirement for non blocking I/O (for the server side effort). That should be builtin from the start.
> This seems possible with OpenSSL, but AFAIK not with CommonCrypto. Which I don’t think is a big deal, because NIO could probably be emulated using threads on macOS. The latter is a dev platform anyways and it should be fine if it doesn’t scale that well …
What do you mean by « NIO is not possible with CommonCrypto ». CommonCryto has no IO API AFAIK. This is just a low level cryptographic library that provide a couple of digest and encryption algorithms. On macOS, the recommended low-level way to do SSL is using the SecurityFramework. And here again, the API is not responsible of the IO handling. So there is not constraint about what you use for IO.
> Summary: Please structure the API so that it works with NIO from the start. Designing something which requires a thread for each SSL connection is hopefully a no-go :->
>> On 29 Jan 2017, at 14:52, Gelareh Taban via swift-server-dev <swift-server-dev at swift.org> wrote:
>> Hi all,
>> The next Security Group meeting will be Monday March 6th, (1-2pm CST) / (11-12am PST) / (7-8pm GMT)
>> The agenda would be to go over the draft group pitch (https://github.com/swift-server/security/blob/master/README.md) and discuss the project design goals and overall approach.
>> password: swiftify
>> swift-server-dev mailing list
>> swift-server-dev at swift.org
> swift-server-dev mailing list
> swift-server-dev at swift.org
More information about the swift-server-dev