Skip to content

Commit 6b2cf90

Browse files
authored
Merge pull request #122113 from poornimanayar/patch-1
Update the link to SignalR Service configuration
2 parents ad701eb + ebd720d commit 6b2cf90

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-signalr/signalr-concept-internals.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,18 +28,18 @@ A self-hosted ASP.NET Core SignalR application server listens to and connects cl
2828
With SignalR Service, the application server no longer accepts persistent client connections, instead:
2929

3030
1. A `negotiate` endpoint is exposed by Azure SignalR Service SDK for each hub.
31-
1. The endpoint responds to client negotiation requests and redirect clients to SignalR Service.
31+
1. The endpoint responds to client negotiation requests and redirects clients to SignalR Service.
3232
1. The clients connect to SignalR Service.
3333

3434
For more information, see [Client connections](#client-connections).
3535

3636
Once the application server is started:
3737

3838
- For ASP.NET Core SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service.
39-
- For ASP.NET SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service, and one per application WebSocket connection.
39+
- For ASP.NET SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service and one per application WebSocket connection.
4040

4141

42-
The initial number of connections defaults to 5 and is configurable using the `InitialHubServerConnectionCount` option in the SignalR Service SDK. For more information, see [configuration](https://github.com/Azure/azure-signalr/blob/dev/docs/run-asp-net-core.md#maxhubserverconnectioncount).
42+
The initial number of connections defaults to 5 and is configurable using the `InitialHubServerConnectionCount` option in the SignalR Service SDK. For more information, see [configuration](signalr-howto-use.md#configure-options).
4343

4444
While the application server is connected to the SignalR service, the Azure SignalR service may send load-balancing messages to the server. Then, the SDK starts new server connections to the service for better performance. Messages to and from clients are multiplexed into these connections.
4545

0 commit comments

Comments
 (0)