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

Allow handler to handle unknown message types #4

Closed
kpdecker opened this issue Sep 4, 2015 · 1 comment
Closed

Allow handler to handle unknown message types #4

kpdecker opened this issue Sep 4, 2015 · 1 comment
Assignees
@hueniverse
Labels
feature New functionality or improvement
Milestone
0.3.0

Comments

@kpdecker
Copy link
Contributor

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 self-assigned this Sep 4, 2015
@hueniverse hueniverse modified the milestone: 0.3.0 Sep 4, 2015
@Marsup Marsup added feature New functionality or improvement and removed request labels Sep 20, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hueniverse hueniverse

Labels
feature New functionality or improvement
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
3 participants
@hueniverse @kpdecker @Marsup