4 ms·
This is because it's the server version. This is equivalent to liveview websites that have roundtrip latency. Do you know if there is a wasm hosted version of t
by mgh95 3y ago
This is because it's the server version. This is equivalent to liveview websites that have roundtrip latency. Do you know if there is a wasm hosted version of this?
- Anon3941 3y agoNot only is it Blazor Server, the web socket connection doesn't appear to work so its fallen back to http polling...
- mgh95 3y agoYeah, the issues here appear to be developer related. The docs offer less practical guidance than they should on proper deployment of blazor applications. I work on a startup that is on WASM (primarily desktop; little to no mobile usage, which limits the negatives of blazor wasm) and it's quite good. We were concerned about load time initially and asked users about the load time. The response was "what load time". Blazor is good for the "right" kind of application, but like many see poor implementation due to limited documentation guidance or worked examples can severely degrade practical implementation.
- ahoka 3y agoIt’s deployed on an all-Microsoft stack and despite that it’s not working. Do MS still makes you think you need to pay for an Azure service to have WS in your app? It used to be the case.