[Epic]: SignalR - .NET7

[rafikiassumani-msft]

S = A few hours
M = A few days (1-5 days)
L = About a week (1 - 2 weeks)
XL = > 2-3 weeks
XXL = ~ Milestone (Needs to be broken down)

Issue	Category	Priority	Size	Status
Crank testing for SignalR (#37909)	testing	P1	M	Committed
SignalR streaming (Broadcast) from server to client (#10151)	client, server, protocol	P3	XXL
Seamless reconnect - Allows the server to retain the buffer and preserve state	client, server	P2	XXL	Stretch goal/re-evaluate
Allow Values to be returned from client invocations (#5280)	client, server	P0	XXL	Committed
Refresh authorization tokens (#5297)	client, server, protocol	P1	XXL
Blazor server + SignalR enhancements (#10407)	client, server	P1	XL
Fix streaming back-pressure - Needs support for flow control in the protocol (#33859)	client, server, protocol	P2	M
Orleans backplane for SignalR	client, server, protocol	P1	XL	Experiment (E2E spike) @bradygaster @halter73 @ReubenBond
AFD (Azure Front Door) connection isssues - No support for websockets (https://github.com/MicrosoftDocs/architecture-center/issues/1891)	Azure		XL	Needs to reach out to Azure team
Docs - dotnet/AspNetCore.Docs#23357	Docs	P2	XL

[ThisWillDoIt]

No Azure Front Door support is a real stopper for adopting SignalR for us.
As SignalR in itself is fine as it is, can we vote somewhere on any Azure board in case this whole EPIC won't be in .NET7?

[BrennanConroy]

can we vote somewhere on any Azure board

https://feedback.azure.com/d365community/idea/c8b1d257-8a26-ec11-b6e6-000d3a4f0789

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 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.