You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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
The text was updated successfully, but these errors were encountered: