QUIC threading model question

[makkarpov]

Hello,

I have a question about the library threading model (both currently implemented and formally specified).

• On server side, is there a guarantee that streamHandler is invoked on the same event loop thread as the associated parent QUIC channel handlers? I.e. is there a usual netty single-threadity guarantee between these two as the regular handlers have? Is such guarantee (if exists) just a current implementation detail, or is it a fully specified part of the API?
• Is there a single-threading guarantee between handlers of different streams of same connection? Current implementation does offer this, but is this a part of the public API?
• On server side, is there a way to schedule different QUIC connections to the different event loops? Or is the server forever forced to run everything on a single thread (including crypto)?
• Is there more formally specified threading model? I.e. current implementation is the one thing, but API guarantees could be weaker to allow for future changes.