ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Architecture note on the Blazor Server circuit model: managing per-circuit state isolation, SignalR trust boundaries, operational checks, and the limits of in-memory state.
Blazor Server keeps component state on the server inside a per‑tab SignalR circuit. Reconnection can restore that state only while the circuit is retained. Once disposed, in‑memory state is lost unless you persisted it.
Learn how to implement a custom CircuitHandler in Blazor Server to track user connectivity, prevent memory leaks, and customize the reconnection UI for a professional user experience.
An architecture note on Blazor Server's cascading authentication state: why the circuit is the real trust boundary, how AuthorizeView fits in, and the reconnection-after-token-expiry failure mode most designs miss.
Blazor Server keeps component state in a server-side circuit. See how client retry limits and server retention periods interact, and how to verify recovery behaviour.
Make Blazor Server survive transient network loss with automatic circuit reconnection, visible reconnect UI, persisted state, and safe fallbacks for permanent disconnects.
The yellow 'reconnecting' banner in Blazor Server means the SignalR circuit died. Learn to read the timing, check the _blazor WebSocket, and match fixes—retention tuning, async handlers, proxy timeouts, sticky sessions—to the actual cause.
Goal: reconcile Blazor Server circuit lifecycle events with reverse proxy WebSocket timeout behavior to maintain persistent connections without unnecessary disconnections. Constraint/uncertainty: SignalR's KeepAliveInterval and AutoDisconnectTimeout are calculated on the client-side circuit handler, but when an intermediate proxy or load balancer terminates
Context Blazor Server maintains a persistent SignalR circuit per user session. When network interruption occurs, the browser console surfaces the documented error The circuit has been disconnected and the server-side circuit terminates. Upon reconnection, a new circuit is established, but component state and initialization logic are not automatically restore
blazor
dotnet