daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Inform readers on support status of stateful reconnect (#32500)

pull/32503/head
Luke Latham 2024-05-02 07:35:45 -04:00 committed by GitHub
parent beb87c2212
commit 107b8d3a0e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
aspnetcore/blazor/fundamentals/signalr.md
View File

@ -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"
<!-- UPDATE 9.0 Remove when support is present -->
## Azure SignalR Service with stateful reconnect
[Stateful reconnect](xref:signalr/configuration#configure-stateful-reconnect) (<xref:Microsoft.AspNetCore.SignalR.Client.HubConnectionBuilderHttpExtensions.WithStatefulReconnect%2A>) 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

5
aspnetcore/blazor/host-and-deploy/server.md
View File

@ -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.
<!-- UPDATE 9.0 Remove when support is present -->
> [!NOTE]
> [Stateful reconnect](xref:signalr/configuration#configure-stateful-reconnect) (<xref:Microsoft.AspNetCore.SignalR.Client.HubConnectionBuilderHttpExtensions.WithStatefulReconnect%2A>) 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"