Draft Hixie 76 Protocol Support

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I already deploy this php server http://code.google.com/p/phpws/
2. The client for the above server is phpws.jmango.net:8080/test.php
3. You can connect to the server using phpws.jmango.net:12345/echo/

What is the expected output? What do you see instead?
The echo server is gonna send back everything you send to it

Kind regards

Original issue reported on code.google.com by ngoccuon...@gmail.com on 27 Sep 2011 at 3:02

[GoogleCodeExporter]

Due to limitation of our router, the server now is phpws.jmango.net.
I dont have the client working for the URL I posted before

Original comment by ngoccuon...@gmail.com on 27 Sep 2011 at 5:15

[GoogleCodeExporter]

Which client is this for? Java/Android or iOS?

Original comment by joshuadmorris@gmail.com on 27 Sep 2011 at 3:10

[GoogleCodeExporter]

Original comment by joshuadmorris@gmail.com on 27 Sep 2011 at 4:29

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm actually really close to a complete hixie76. I just need to fix a bug or 
two in the handshake code and this can be up and running. I am currently 
working on a refactoring to simplify the whole thing, but I should be able to 
do this as part of the next release.

Original comment by joshuadmorris@gmail.com on 27 Sep 2011 at 4:57

[GoogleCodeExporter]

HI Josh

The support I'm working on is for iPhone.

I read your code in WebSocket00, you really are close to complete that protocol.
I tried to fix it but still it is not working currently

Kind regards

Original comment by ngoccuon...@gmail.com on 28 Sep 2011 at 2:18

[GoogleCodeExporter]

HI Josh

I got this library in Java up and running for Hixie 76
http://code.google.com/p/weberknecht/
What I'm trying to do is to convert this logic to objective-C to make it work, 
but still struggling

Kind regards

Original comment by ngoccuon...@gmail.com on 29 Sep 2011 at 1:37

[GoogleCodeExporter]

I am going to push to wrap this up over the weekend, but it might drip into 
next week.

Original comment by joshuadmorris@gmail.com on 29 Sep 2011 at 2:08

[GoogleCodeExporter]

It's not perfect, but try using the WebSocket00.h header now and see if it 
meets your needs. You can check out UnittWebSocketClient00Tests for sample code 
connecting to ws://echo.websocket.org.

Original comment by joshuadmorris@gmail.com on 2 Oct 2011 at 9:06

• Changed state: Fixed

[GoogleCodeExporter]

It's checked into the trunk. I will do a build after I validate one or two more 
things.

Original comment by joshuadmorris@gmail.com on 2 Oct 2011 at 9:07

[GoogleCodeExporter]

Hi Josh

Thanks for the good  try. In the scope of my project, I only need to send data 
to the server so I already worked out the sending part for it.

I discover one over-released object which caused BAD_EXE_ACCESS in this line
return [NSError errorWithDomain:AsyncSocketErrorDomain 
code:AsyncSocketConnectTimeoutError userInfo:info];
in AsynSocket.m

Later this object will be released twice.

How to reproduce this error:
Get server timeout twice

Kind regards

Original comment by ngoccuon...@gmail.com on 3 Oct 2011 at 11:57

[GoogleCodeExporter]

Original comment by joshuadmorris@gmail.com on 9 Oct 2011 at 2:30

• Changed state: Verified