search

Nethravathitcs / unitt

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

Timeout connecting to grizzly backend #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. try to establish connection to backend using Glassfish 3.1 with grizzly
2.
3.

What is the expected output? What do you see instead?
Expected a connection but got a timeout on iphone and broken pipe exception on 
java backend

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

Please provide any additional information below.

Original issue reported on code.google.com by JonNoerr...@gmail.com on 5 Jul 2011 at 10:08

GoogleCodeExporter commented 8 years ago 
Which WebSocket were you using? 00 or 07?

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

GoogleCodeExporter commented 8 years ago 
I did some homework and it appears that even the latest version of Grizzly code 
in svn is using 06, not 07. The primary difference, is that 06 does not mask 
the data and 07 requires the client to mask its data. This is causing the 
server to misread the data. I was able to connect successfully, but I could not 
send any data that the server would handle correctly. Again, this is because 
the headers are defined differently and Grizzly is incorrectly detecting the 
data length of 07 data frames.

Original comment by joshuadmorris@gmail.com on 6 Jul 2011 at 3:22

GoogleCodeExporter commented 8 years ago 
Impressive responsetime. Thank you.

I was using 07, and was not aware of the different protocol versions. Will I be 
able to use 00 with grizzly? I.o.w. is 06 backward kompatible?

Original comment by JonNoerr...@gmail.com on 6 Jul 2011 at 5:44

GoogleCodeExporter commented 8 years ago 
Unfortunately, I did not see support for 00 at all. It only appears to support 
06, which is not backwards compatible with anything. I know Jetty supports 00, 
06, & 07. I haven't had a chance to check out Netty yet. All of the servers 
have a very similar interface you can use. There is some form of "onOpen", 
"onClose", "onMessage", etc. There should be very little difficulty in moving 
between them from a web socket perspective. Of course, this does nothing to 
help you if the rest of your app requires a specific J2EE server.

Original comment by joshuadmorris@gmail.com on 6 Jul 2011 at 3:11

GoogleCodeExporter commented 8 years ago

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