Closed metabench closed 8 years ago
Hi @metabench
This is by design: connection.send()
sends the whole content as one frame, and the receiving side isn't expecting anything larger than 2MiB.
You can either/both:
connection.beginBinary()
on the sending sideYou could tell the problem was this because the connection got closed with error 1009, as per the spec:
1009 indicates that an endpoint is terminating the connection because it has received a message that is too big for it to process.
Hope it works for you. If it doesn't let me know ;)
I am making a distributed application that sends approx 12 MB of data to worker threads, and I'm trying to do so with nodejs-websocket. Currently I can't tell if the failure is on sending or receiving.
Has this package been tested with larger amounts of data, in the tens of MB?
Would it be worth being clear about what size limits there are for messages?
I am sending with: