Matt Caswell

> It should be possible to make simple blocking clients (e.g. demos/bio/s_connect.c) work with a single line change: The "single line change" is probably unrealistic. Let's say minimal changes instead....

Minor tweak pushed clarifying how `SSL_new_stream` works.

Pushed to master and 3.0.

This seems more like a plesk issue than something OpenSSL can advise you on. You would be better off asking in some plesk forum.

Hint: to read the document and see the images inline, from the "Files changed" tab above click the 3 dots "..." in the top right hand corder of the quic-event-loop.md...

> You should really start from the design of current applications and think how OpenSSL would be used by these applications, otherwise you may create something that will not work,...

> The “application selects” API is the most important one. Event-loop implementations are highly system-specific and performance-critical, and OpenSSL does not want to be implementing them. I agree. This seems...

> Any sort of event loop that OpenSSL tried to support would need to cover a huge variety of platforms. Linux epoll and io_uring, Windows IOCP and IoRing, and *BSD...

> ```` c > switch (x) { > case 1: > stmt; > break; > case 2: { > decl somevar; > > stmt-with-somevar; > another-stmt; > break; > }...

> Maybe we should have something like int X509v3_addr_get_safi(unsigned *safi); return 1 on success and modify the safi's value if we want to fully comply with the standard, or maybe...