unitt-project

Josh et al, We're looking into providing some server side redundancy and were wondering if there

The client is finally release quality. The GCD functionality is working and allows for full

The iOS client is now in a good place. While it is being tested, I am moving my focus to updating the

All known issues have been fixed. The product now passes all Autobahn RFC6455 compliance tests.

Changes Include: - Fully RFC6455 compliant. - Fixed various fragmentation bugs The client is very

Now that all known defects have been addressed, I am beginning work on updating the web socket

Fixed a number of issues and enabled versions of Android prior to 2.3. - fixed an issue where the

Fixed a number of bugs, including: - fixed an issue where close bytes were sent in the wrong order -

I apologize for being away from this project for the last few weeks, but between the holidays and the

Sorry for the delay in responding to you. My daughter was just born about the time you posted your

You generally want to avoid putting any business logic in your UI thread. I think this is especially

Thanks! It would be great! As a side note: I will see if I can test if the socket goes down if the

I will be adding the InterruptedException for a build that I should have out next week. Things have

Thanks, I am going to try it. Cheers, Ivan On Oct 18, 5:48 am, Josh Morris <joshuadmor...@gmail.

I figured it out and now I feel stupid. Turns out we were using an old version of WebSocketClient

I will get a new build out this coming week. Sorry for the delay, but work got crazy! On Oct 10, 10:

- added support for custom headers - fixed an error on sending close (could loop in certain

I understand now. You want a lightweight server to host web socket code, not to connect to. The

Both clients now support supplying your own headers in the config. It is a simple list and will be

I have updated the WebSocket00.h file in SVN to work with the Hixie76 stuff. I will be releasing a

I have updated the WebSocket00.h to work with the ws://echo.websocket.org service described in your

- fixed an issue where in certain situations the header host parameter was missing a port entry

- fixed an issue where in certain situations the header host parameter was missing a port entry -

Java/Android WebSocket client/server implementation for rev07, rev08, rev10. This is working with

- Fixed an issue where messages whose length was a product of the max payload size were missing their

- added rev08 & rev10 - added close status & message - added timer to force close on timeout

Good catch! Fixed in 2.6. Look for a build in the next hour or so. On Jul 26, 2:23 pm, Paul Dardeau

- Fixed error with fragments not being parsed if they are part of a long chain - Close mechanics now

- Fixed message length issues - Fixed continuation cut off

Oops - wrong thread. On Jun 30, 9:44 pm, Josh Morris <joshuadmor...@gmail.com> wrote: > -