Skip to content
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

Open
sirsquall opened this issue Feb 12, 2014 · 7 comments
Open

Sending big message through websocket #49

sirsquall opened this issue Feb 12, 2014 · 7 comments

Comments

@sirsquall
Copy link

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.

@EralpB
Copy link

EralpB commented Mar 4, 2017

This is unfortunately true :(

@aaronxdd
Copy link

@sirsquall me too,have you solve the problem

@EralpB
Copy link

EralpB commented May 15, 2017

@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.

@sirsquall
Copy link
Author

We decreased the size, if I remember well, but I'm not sure now, @dsnoeck do you remember?

@aaronxdd
Copy link

@sirsquall if i want to send data which is bigger than 16kb,how to solve it

@dsnoeck
Copy link

dsnoeck commented May 15, 2017

Checking at the code, we kept it to 16kb:
this.maxWebSocketFrameSize = 16 * 1024;

@KrzysZG37
Copy link

Did anybody solve the issue? Increasing maxWebSocketFrameSize on the client and server side didn't solve the problem for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants