search

nmkhoa / unitt

Automatically exported from code.google.com/p/unitt
0 stars 0 forks source link

binary message > 16K trunated #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Send a binary message > 16K bytes from a version 7 websocket server (using 
Worlize node.js version 7)
2.
3.

What is the expected output? What do you see instead?
Only the first 16K of the binary message arrives in didReceiveBinaryMessage. 
I've verfied (in the debugger) that the rest of the binary message arrives, but 
it appears to be thrown away. i.e. the handleCompleFragment method in 
WebSocket07.m believes that aFragment.isFinal == YES. 

I'm continuing on down into the code, but I thought I'd give you a heads up.

What version of the product are you using? On what operating system?
Latest version, on Mac OSX-10.6.6

Please provide any additional information below.

Original issue reported on code.google.com by interfac...@gmail.com on 30 Jun 2011 at 8:59

GoogleCodeExporter commented 8 years ago 
I found the issue. It has been fixed in v2.3. Let me know if you have any other 
issues.

Original comment by joshuadmorris@gmail.com on 1 Jul 2011 at 1:57

GoogleCodeExporter commented 8 years ago 
I am assuming that this is fixed. I have verified it in the latest build.

Original comment by joshuadmorris@gmail.com on 12 Jul 2011 at 6:14