-
Notifications
You must be signed in to change notification settings - Fork 586
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
Sending big message through websocket #49
Comments
This is unfortunately true :( |
@sirsquall me too,have you solve the problem |
@aaronxdd I remember solving this issue in a messaging protocol by enabling the "binary message" option. (although the messages were not binary.. but doesn't matter) I am not sure if this was THE library though. |
We decreased the size, if I remember well, but I'm not sure now, @dsnoeck do you remember? |
@sirsquall if i want to send data which is bigger than 16kb,how to solve it |
Checking at the code, we kept it to 16kb: |
Did anybody solve the issue? Increasing maxWebSocketFrameSize on the client and server side didn't solve the problem for me. |
When you send a message through Stomp Websocket using stomp.js, if you increase the size of "maxWebSocketFrameSize", to be able to send a big message without spliting, we have a "Connection Lost" if the message is bigger thank 16kb.
The text was updated successfully, but these errors were encountered: