Hugo Landau

>An application can (optionally) insert new connections into the connection queue directly by calling `SSL_EVENT_CTX_add_new_connection()`. This would also result in a "new connection" event being issued. Ordinarily new connection events...

My thoughts for connection migration are roughly as follows: - We need to have a plan for this in the API now. Shipping an MVP lets minimize the *functionality* we...

The trigger would be a decision to do connection migration. Are we assuming connection migration is always initiated by the application? Generally I would expect connection migration to be triggered...

The trouble is QUIC is basically replacing transport protocols ordinarily provided in kernel mode. The precedent would be how protocols like kernel-mode SCTP handle migration, as well as how other...

* It should be possible to make simple blocking clients (e.g. demos/bio/s_connect.c) work with a single line change: ```diff - ssl_ctx = SSL_CTX_new(TLS_client_method()); + ssl_ctx = SSL_CTX_new(QUIC_client_method()); ``` * QUIC...

>The "single line change" is probably unrealistic. Let's say minimal changes instead. Yeah, agreed. I've put together my thoughts on a possible process for getting an API which meets the...

I expect this is having difficulty getting reviews due to lack of VMS experience. Though I have no direct experience with VMS, this patch looks right to me, and I've...

Merged to master. Thank you. This does not cherry-pick cleanly to 3.0 or 1.1.1, will need another PR.

The errno packing thing is a bit goofy. Could just add an `int *err` argument. WSASendMsg requires Vista so needs `_WIN32_WINNT` to be bumped to 0x0600. Could probe for it...

It turns out WSASendMsg and WSARecvMsg, which were introduced in Vista, are not exported as normal symbols by Windows. Instead, you have to use them by obtaining function pointers to...