From 107b8d3a0ec82f4209848732e849071e12920d29 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 2 May 2024 07:35:45 -0400 Subject: [PATCH] Inform readers on support status of stateful reconnect (#32500) --- aspnetcore/blazor/fundamentals/signalr.md | 10 ++++++++++ aspnetcore/blazor/host-and-deploy/server.md | 5 +++++ 2 files changed, 15 insertions(+) diff --git a/aspnetcore/blazor/fundamentals/signalr.md b/aspnetcore/blazor/fundamentals/signalr.md index b34d1197a7..afad71c6b6 100644 --- a/aspnetcore/blazor/fundamentals/signalr.md +++ b/aspnetcore/blazor/fundamentals/signalr.md @@ -20,6 +20,16 @@ Server-side apps use ASP.NET Core SignalR to communicate with the browser. [Sign Blazor works best when using WebSockets as the SignalR transport due to lower latency, reliability, and [security](xref:signalr/security). Long Polling is used by SignalR when WebSockets isn't available or when the app is explicitly configured to use Long Polling. +:::moniker range=">= aspnetcore-8.0" + + + +## Azure SignalR Service with stateful reconnect + +[Stateful reconnect](xref:signalr/configuration#configure-stateful-reconnect) () was released with .NET 8 but isn't currently supported for the Azure SignalR Service. For more information, see [Stateful Reconnect Support? (`Azure/azure-signalr` #1878)](https://github.com/Azure/azure-signalr/issues/1878). + +:::moniker-end + :::moniker range=">= aspnetcore-9.0" ## WebSocket compression for Interactive Server components diff --git a/aspnetcore/blazor/host-and-deploy/server.md b/aspnetcore/blazor/host-and-deploy/server.md index ee5586dfa4..072d1b8d6b 100644 --- a/aspnetcore/blazor/host-and-deploy/server.md +++ b/aspnetcore/blazor/host-and-deploy/server.md @@ -72,6 +72,11 @@ Recommendations for global deployments to geographical data centers: For Blazor Web Apps that adopt interactive server-side rendering, consider using the [Azure SignalR Service](xref:signalr/scale#azure-signalr-service). The service works in conjunction with the app's Blazor Hub for scaling up to a large number of concurrent SignalR connections. In addition, the service's global reach and high-performance data centers significantly aid in reducing latency due to geography. If your hosting environment already handles these concerns, using the Azure SignalR Service isn't necessary. + + +> [!NOTE] +> [Stateful reconnect](xref:signalr/configuration#configure-stateful-reconnect) () was released with .NET 8 but isn't currently supported for the Azure SignalR Service. For more information, see [Stateful Reconnect Support? (`Azure/azure-signalr` #1878)](https://github.com/Azure/azure-signalr/issues/1878). + :::moniker-end :::moniker range="< aspnetcore-8.0"