SignalR QUIC

[alexiordan]

Is it expected to have SignalR running on top of QUIC?

From here it seems to be possible:

So SignalR is built against this and has no idea what the underlying trsnpsort is, it just parses it’s protocol over the “transport”. So IPC becomes interesting, SignalR over named pipes? Easy, tcp easy, QUIC (hopefully easy).

— David Fowler (@davidfowl) March 30, 2018

Are there any plans on that?

[davidfowl]

Not yet, we're doing experiments but it's way too early to promise anything.

[campersau]

For HTTP/3 there is also a WebTransport under development which could potentially be used as a transport by SignalR which would then also work in the browser.
https://web.dev/webtransport/

[wegylexy]

Can't wait. I just implemented a way to use any IDuplexPipe or Stream (e.g. QuicStream in preview for .NET 7.0) as the underlying transport.
See FlyByWireless.SignalRTunnel and FlyByWireless.SignalRTunnel.Client.
Once you've got a bidirectional stream set up, forward it to the hub connection handler on the server and the hub connection builder in the client. If you use multiple QUIC streams for other purposes, feel free to send custom data and consume all of them before handing it over to my extensions.

For WebTransport, I hope it would work similarly, that I could have multiple data channels and pass just one over to SignalR.

[yahorsi]

No once QUIC experimental implementation is out, are there any samples how it can be used with SignalR, interested in trying SignalR streaming with QUIC

[wegylexy]

In my case, I use QUIC datagrams to synchronize real-time game states and QUIC streams for occasional data, all multiplexed over one single connection per native game client. There are also web clients that can only use WebSockets to interact with those occasional data. Using the same SignalR APIs enables more code reuse across the full native game client, the server, auxiliary web clients, and third-party extensions in my case.