Closed as not planned
Description
I like the blazor server side concept using SignalR which is connected.
Can it not be made disconnected, so that it can handle more clients, becuase current connected architecture has scaling issues.
There are many applications that can take advantage of it by using polling nature instead.
- Flight status usuall you only want to check or get flight status every minute or so, so connected client just waste the resource.
There is no need of realtime information, just need to poll to get information every minute or so(or let it be configurable by user) - Let user load the page and be diconnected and reconnect again when user is ready to get more details.
There could be form that user can take of minute or more to fill and he staying connected is just wasting the resource, let him conitnue submiting the form once he clicks submit button,
By not holding on live connecttion server could be serving ohter clients and thereby increase the scaling nature. - I understand there is a webassembly version of Blazor that can help achieve all this, but it is very heavy on dowload.
Would like to know what prevents servside blazor from using disconnected implementation of SignalR rather than connected one? We are listning to events on client side anyway.
You could have both versions, let user opt between realtime one or disconnected one for the server side blazor.
The serverside already has a hughe advantage by keeping client thin, excep that it cannot scale really good.
Metadata
Metadata
Assignees
Labels
This issue is related to the experience of Signal R and Blazor working togetherThis issue impacts only small number of customersIncludes: Blazor, Razor ComponentsThis issue represents an ask for new feature or an enhancement to an existing oneIssues that make Blazor server experience different of Web assembly or DesktopThis label is used by an internal tool