Add support for WebTransport

[scalablecory]

With QUIC incoming, WebSockets is being retired in favor of WebTransport. Consider implementing an API for this.

WebSockets may have fallen out of favor versus e.g. gRPC; I don't know enough about the landscape here. @rynowak @davidfowl @JamesNK any idea?

[ghost]

Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.

[davidfowl]

cc @BrennanConroy this looks super interesting for signalr.

This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server, implementing pluggable protocols underneath with common APIs on top

☺️

[halter73]

In the browser, gRPC-web client-streaming is still very new. SignalR still uses WebSockets as its primary transport.

[wegylexy]

I wish SignalR can take advantage of reliable streams and unreliable datagrams of WebTransport.

[MeydanOzeri]

any update on that ? is it planned anytime soon ?

[wegylexy]

Since the QUIC datagram extension is not yet RFCed, I wouldn't expect it in .NET 6 soon even though msquic already supports it.

[wegylexy]

How possible is it to inject custom transport implementation for non-browser use cases? e.g. replace WebSocket with a QUIC stream to share an existing QUIC connection in another custom service. I can think of intercepting the Redis backbone.

[davidfowl]

@wegylexy it's not clear what you're asking for here. Where do you want to replace the transport?

[wegylexy]

@davidfowl in addition to WebSocket, long polling, and server push, I want to add a custom transport by implementing certain interfaces (dependency injection), without baking it into the runtime.

[davidfowl]

@davidfowl in addition to WebSocket, long polling, and server push, I want to add a custom transport by implementing certain interfaces (dependency injection), without baking it into the runtime.

But what does that mean? Add a custom transport to what? Are you talking about SignalR?

[wegylexy]

Oh, ya. Didn't notice the original issue is not scoped to SignalR. Yes, I just want to inject a custom SignalR transport.

[wegylexy]

I figured that I can inject clients from QUIC connections into HubLifetimeManager<> in a custom hosted service via a dedicated stream, without touching internal SignalR transports.

[wegylexy]

Let's see how https://github.com/wegylexy/webtransport may be incorporated into the runtime.

[ghost]

Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.

Issue Details

---

With QUIC incoming, WebSockets is being retired in favor of [WebTransport](https://w3c.github.io/webtransport/). Consider implementing an API for this. WebSockets may have fallen out of favor versus e.g. gRPC; I don't know enough about the landscape here. @rynowak @davidfowl @JamesNK any idea?

Author:	scalablecory
Assignees:	-
Labels:	`api-suggestion`, `area-System.Net.Http`
Milestone:	Future