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

Failing/Missing TCP Packet buffering for incoming WebSocket frames #5472

Closed
repomaa opened this issue Oct 19, 2015 · 3 comments
Closed

Failing/Missing TCP Packet buffering for incoming WebSocket frames #5472

repomaa opened this issue Oct 19, 2015 · 3 comments

Comments

@repomaa
Copy link

repomaa commented Oct 19, 2015

I opened an issue for nodejs about this but I suspect this actually might be a bug in how meteor handles the websocket frame packets. See nodejs/node#3445

@martijnwalraven
Copy link
Contributor

Are you sure this is an issue that is specific to Meteor and not expected behavior for the WebSocket protocol? I've never come across this issue with any other WebSocket client.

@repomaa
Copy link
Author

repomaa commented Oct 21, 2015

I can't believe this is expected behavior because the TCP maximum theoretical packet size is 64KiB which is way less than the maximum size allowed for WebSocket.

@martijnwalraven
Copy link
Contributor

I noticed you already opened an issue for faye-websocket, which Meteor ultimately uses for its WebSocket support. I hope someone there is able to help you with your question.

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

2 participants