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.

Sign up for GitHub

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

Jump to bottom

Provide access to client disconnection #108

Open
swishy opened this issue Jan 10, 2017 · 1 comment
Open

Provide access to client disconnection #108

swishy opened this issue Jan 10, 2017 · 1 comment
Assignees
@swishy

Comments

@swishy
Copy link
Collaborator

swishy commented Jan 10, 2017

Currently wasabi provides no mechanism for developers to be notified when a websocket client disconnects, this needs to be resolved so they can release contexts, this is also an issue internally as wasabi doesn't clear out clients associated with handlers
@swishy swishy self-assigned this Jan 10, 2017
@swishy swishy mentioned this issue Jan 10, 2017
Closed
@swishy
Copy link
Collaborator Author

swishy commented Jan 16, 2017

Initial implementation done, needs more testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@swishy swishy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swishy