Skip to content

Conversation

@Davidiusdadi
Copy link
Collaborator

Some more tests still have to be done.

…, onWebsocketClosing, onWebsocketClose to give the user more insights/control over the different steps during the close handshake. This is especially necessary because of the asynchronous nature of the implementation.
…ck).

Instead of a java.nio.channels.NotYetConnectedException a new org.java_websocket.exceptions.WebsocketNotConnectedException will be thrown.
Formatted code and started to renaming the inexpressive conn variables.

The state getter methods still have to be touched.
…d the currently connected websockets. (TooTallNate#138)

Also removed the setAddress method since it is misleading and unnecessary.
Davidiusdadi added a commit that referenced this pull request Dec 11, 2012
bugfixes and more elaborate close callbacks and added onMessageFragment callback
@Davidiusdadi Davidiusdadi merged commit c9b4dbc into TooTallNate:master Dec 11, 2012
maakolk pushed a commit to maakolk/Java-WebSocket that referenced this pull request Mar 5, 2017
bugfixes and more elaborate close callbacks and added onMessageFragment callback
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.

2 participants