nmkhoa / unitt

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

Receive large data from server #43

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Hey, I been using the unittwebsocket to send and receive data from a tornado 
webserver all working good except on large data size.

the server & unittwebsocket are set to work with the rfc6455

I changed the payload in unittwebsocket to 5 * 1024 * 1024 (5MB) and been able 
to send to the server large binary data.

the server sends the data back as it should but the unittwebsocket does not 
parse the header correctly and my app is crashing.
I also tried to encode the same data with base64 and send it as string but 
still the problem is the same.

for some reason the tornado server does not even tries to split the data into 
fragments it always send it as one fragment (if anyone familiar with tornado 
server as well maybe can elaborate on that issue) maybe splitting the data from 
the server side will solve the problem for me on the unittwebsockt side

What steps will reproduce the problem?
1. try to receive large data from websocket server

What version of the product are you using? On what operating system?
0.9.3

Please provide any additional information below.

Attached is the relevant exception log.

Thank you.

Original issue reported on code.google.com by d...@omniscience.co.il on 16 May 2012 at 10:00

Attachments:

GoogleCodeExporter commented 8 years ago
I will take a look at this. I have tested the client receiving and sending up 
to 16MB payloads without issue. But there could be a bug buried in there. I 
should be able to take a look at this over the weekend.

Original comment by joshuadmorris@gmail.com on 17 May 2012 at 5:25

GoogleCodeExporter commented 8 years ago
Hey,
Any updates about this issue?

Original comment by d...@omniscience.co.il on 3 Jun 2012 at 1:25

GoogleCodeExporter commented 8 years ago
I am now actively working this. I am trying to get a release candidate out for 
the Java/Android client now that I have done so for the iOS one. Should be 
something in the next week or two (at the latest).

Original comment by joshuadmorris@gmail.com on 11 Jun 2012 at 9:34