Demi Marie Obenour

> We've discussed possibly supporting this, but never came to and hard conclusion. How would you actually use this, if we added support? There is significant work involved and we...

> > That said, I would not be surprised if some people have ruled out MsQuic as an option because of this without filing an issue. > > Perhaps. There...

> I would actually be slightly scared to put the QUIC workers on the UI thread in Node.js. Unlike the current TCP and UDP implementations, which do a TINY amount...

> > That said, I would not be surprised if some people have ruled out MsQuic as an option because of this without filing an issue. > > Perhaps. There...

@nibanks so one thought I had is to allow the MsQuic event loop to handle other things as well, such as pollable file descriptors on Unix and I/O completion ports...

> ### Describe the feature you'd like supported > Dynamic cert: The caller provides a callback that is invoked when the server asks for a certificate. The input is the...

@wfurt Often, the actual signing will itself need to be async, too. Consider a key on a smart card, which is very slow.

NGINX has a bespoke QUIC implementation I believe, but I would prefer to use this one, as it is written in a safer language.

> Two months later, the PR was improved (thanks @dra27) but is still waiting for a review by someone who understands Github's infrastructure and permission model, if this exists. Looks...

> Thanks for the second opinion. It's well known that security fixes receive the least amount of reviewing among all contributions :-( I'll merge and we'll see what happens. You’re...