Giters

peterhajas / Genesis

Edit and test source code, right on your iOS device!

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

"Message was not in compressed format." on message receipt

peterhajas opened this issue · comments

commented

If I force the client to accept any version number (to temporarily fix #6), the client cannot interpret messages from the server as they are not in compressed format.

These issues may relate to the recent switch from JSONKit to NSJsonSerialization.

commented

network manager needs to do login after connecting (via the callback). Otherwise it is async behavior where login could be sent before verifying the protocol version (connection handshake).

  • Jeff

On Saturday, April 21, 2012 at 1:04 AM, Peter Hajas wrote:

If I force the client to accept any version number (to temporarily fix #6), the client cannot interpret messages from the server as they are not in compressed format.

These issues may relate to the recent switch from JSONKit to NSJsonSerialization.

Reply to this email directly or view it on GitHub:
#7

commented

Thanks Jeff!

Is this the issue I was experiencing? If I log in in an asynchronous behavior, is the API functional?
On Apr 21, 2012, at 5:19 PM, Jeff Hui reply@reply.github.com wrote:

network manager needs to do login after connecting (via the callback). Otherwise it is async behavior where login could be sent before verifying the protocol version (connection handshake).

  • Jeff

On Saturday, April 21, 2012 at 1:04 AM, Peter Hajas wrote:

If I force the client to accept any version number (to temporarily fix #6), the client cannot interpret messages from the server as they are not in compressed format.

These issues may relate to the recent switch from JSONKit to NSJsonSerialization.

Reply to this email directly or view it on GitHub:
#7

Reply to this email directly or view it on GitHub:
#7 (comment)

commented

This has been fixed with asynchronous login.