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

Enhance Blazor Server sticky sessions requirement (#19731)

pull/19743/head
Luke Latham 2020-09-01 05:23:33 -05:00 committed by GitHub
parent 4729472c72
commit 31aa7731d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
aspnetcore/blazor/hosting-models.md
View File

@ -69,6 +69,9 @@ The Blazor Server hosting model offers several benefits:
* Thin clients are supported. For example, Blazor Server apps work with browsers that don't support WebAssembly and on resource-constrained devices.
* The app's .NET/C# code base, including the app's component code, isn't served to clients.
> [!IMPORTANT]
> A Blazor Server app prerenders in response to the first client request, which sets up the UI state on the server. When the client attempts to create a SignalR connection, **the client must reconnect to the same server**. Blazor Server apps that use more than one backend server should implement *sticky sessions* for SignalR connections. For more information, see the [Connection to the server](#connection-to-the-server) section.
There are downsides to Blazor Server hosting:
* Higher latency usually exists. Every user interaction involves a network hop.