-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Decide if server-side Blazor needs limits on how many events can be delivered and the max size for events #12003
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
Comments
Do you have any data or examples of tests that help us understand the priority of this? |
In process, so far with a client I can cause exceptions on the server
And I get the memory from the server to grow up to 3GB |
Doesn't SignalR enforce a default limit on the message size from a client? How will an external client run code in process on a deployed application? |
I meant with 1 client.
Yes, I'm playing within those rules. Sending events with 31K. The default signalr message size is 32K |
Ok good, this seems relevant then 👍 |
Closing this as we've found out that things look good enough and we don't need to do anything here. |
No description provided.
The text was updated successfully, but these errors were encountered: