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

Expose socket state #2

flowersinthesand opened this issue Jun 4, 2015 · 0 comments

Expose socket state #2

flowersinthesand opened this issue Jun 4, 2015 · 0 comments


Copy link

@flowersinthesand flowersinthesand commented Jun 4, 2015

The original purpose is to regard socket as stateless by forcing user to create a socket action and pass it to server's selector method like all(Action<Socket> action) or byId(String id, Action<Socket> action). However, we have no option but to admit that socket is stateful as it is required to deal with socket whose connection is disconnected for a little while.

A need to expose socket state is to determine socket state at any time of course. For example, user might want to cache some events on cache event which couldn't be sent due to temporal disconnection and send them again on open event. If a connection is broken abruptly in triggering open event handler, it may cause infinite loop so that it should check if socket is in opened state or not.

@flowersinthesand flowersinthesand added this to the 1.0.0-Alpha2 milestone Jun 4, 2015
@flowersinthesand flowersinthesand self-assigned this Feb 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant