Nick Banks

@tmshort it seems like there might be issues with sending session tickets (with quictls v3.0.*): ``` [1]14C0.04D8::2022/11/04-11:10:50.254068500 [Microsoft-Quic][conn][0x23E06066710] Encoded 30 bytes for QUIC TP [1]14C0.04D8::2022/11/04-11:10:50.254072500 [Microsoft-Quic][conn][0x23E06066710] Sending ticket data, 48...

Yes, eventually we plan to add support. There is no timeline for that yet.

Going to close this as it's been opened for nearly 2 years, with no progress nor actual ask for this. We can reopen if anyone every has a scenario where...

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 wouldn't...

> 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 is a reason...

> Is the current model compatible with Node.js, for example, or would that require marshalling? I have no experience with Node.js so I cannot answer that.

> How does that compare to the current TLS client and server? Again, I don't know how that's currently done in Node, but TLS is **very** expensive, so I'd assume...

> At a minimum, I would like to be able to integrate my own code into MsQuic’s event loop somehow. I might need to handle HTTP/1.1 and HTTP/2 traffic as...

> @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...

Is there a way for us to onboard a build to our CI for this?