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

Allow handler to handle unknown message types #4

Closed
kpdecker opened this issue Sep 4, 2015 · 0 comments
Assignees
Labels
Milestone

Comments

@kpdecker
Copy link
Contributor

@kpdecker kpdecker commented Sep 4, 2015

Users should be able to handle messages not understood by nes on the websocket channel with a custom handler. The primary use case here is supporting legacy clients who are not using the nes-based protocol and routing.

@hueniverse hueniverse added the request label Sep 4, 2015
@hueniverse hueniverse self-assigned this Sep 4, 2015
@hueniverse hueniverse closed this in 3b078a7 Sep 4, 2015
@hueniverse hueniverse modified the milestone: 0.3.0 Sep 4, 2015
@Marsup Marsup added feature and removed request labels Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.