Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Closed or end callback when using websocket in some case #218

Open
logerzhu opened this issue Aug 4, 2014 · 0 comments
Open

No Closed or end callback when using websocket in some case #218

logerzhu opened this issue Aug 4, 2014 · 0 comments

Comments

@logerzhu
Copy link

logerzhu commented Aug 4, 2014

If the webSocket connect success but just was closed before set the callback, is there any way to check this case?

AsyncHttpClient.getDefaultInstance().websocket(get, "my-protocol", new WebSocketConnectCallback() {
@OverRide
public void onCompleted(Exception ex, WebSocket webSocket) {
//....webScoket disconnect because the network not stable
webSocket.setClosedCallback(...);
webSocket.setEndCallback(...);
}
}

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

No branches or pull requests

1 participant