Skip to content

Conversation

@koush
Copy link

@koush koush commented May 4, 2012

Does not support message or JSON Message. Not sure why that is necessary, as node's socket IO only really recommends using the event message. The other two seem deprecated.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backported this to Froyo, was missing this function.

@skyisle
Copy link

skyisle commented Aug 22, 2012

+1

mike-stewart and others added 17 commits November 29, 2012 14:04
Missing semi-colon in example code.
In the SocketIOClient, `onConnect()` never called `mHandler.onConnect()`
If a message from the socket.io server is emitted with no arguments, it
now is properly received
Fixed crash on a no-argument message
Fixed a bug with incorrect URL when base URI with trailing slash is used.
Fire onConnect event when connection established
Fix logic error from the javascript port.
Client will now send a heartbeat back to the server when it receives one, so the connection won't time out. 
Removed unreachable catch block in cleanup() method, and changed WebSocketClient.Handler() to a Listener() to match the recent change to to the WebSocketClient interface.
Changed print statements to use Log, to be consistent with the rest of the package.
Added heartbeat replies, fixed two bugs, and added logging.
Create an SSL socket for https connections.
Added support for Message and JSONMessage
vinaysshenoy and others added 8 commits March 2, 2013 09:48
Fixed double firing of onConnect().
I converted my application from AutobahnAndroid to android-websockets
to take advantage of ssl support.
android-websockets did not have a isConnected method, which is used in
my application, so I implemented one.
add isConnected method and remove incorrect annotations.
@koush koush closed this Apr 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants