Consider a system for "muxed" connections

[bradygaster]

Design a way to allow “muxed” connections so the Server would still need to make an outbound connection to itself or the service, but it would be one connection and all the actual virtual connections would be tunneled through it (like how the Service connects to the Server today). cc @anurse @danroth27 @halter73

During 3.0, we're currently committing to an implementation design, but not to the implementation.

[analogrelay]

Clearing the milestone. We'll milestone it in Triage. I'd like to keep things out of the 3.0.0 milestone unless they are epics.

[analogrelay]

We'll do some spiking and design work where we can in 3.0. Putting in preview 7 with low priority.

[analogrelay]

We know (and knew when filing this) that we can't get it done for 3.0. This was originally just tracking the design process. Moving to the backlog to clarify that and renaming to cover the actual work.

[analogrelay]

For context: This is a way to make using SignalR from Blazor server-side not suck.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.