-
Notifications
You must be signed in to change notification settings - Fork 25.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8.0 Update: SignalR Config: stateful reconnect #30829
Conversation
@BrennanConroy, I added a new Configure stateful reconnect section based on what we just published in the What's New. |
aspnetcore/signalr/configuration.md
Outdated
|
||
The `StatefulReconnectBufferSize` option is optional with a default of 100,000 bytes. | ||
|
||
* Update the server hub endpoint configuration to enable the `AllowStatefulReconnects` option: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be listed first. Server must allow stateful reconnect otherwise client settings are ignored.
We also don't need to put it for both clients, if it's at the top that should be obvious 😄
Removed repeated statements, cleaned up.
Moved server example to top, cleaned up.
Updated ms.date
cleaned up
I introduced merge conflicts I can't get to resolve. Quickly closing this PR and re-opening to add my changes to a clean version. Sorry. |
Fixes #30674
Added new section: Configure stateful reconnect
Internal previews