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

Create connectResponse for initial response to connect, rather than hacky Happy response #17

Open
tannerpreiss opened this issue Jan 30, 2017 · 0 comments

Comments

@tannerpreiss
Copy link

Using a defined response structure for the connect response will be cleaner and less error-prone.

I think we have to do this as a response message because I have been unable to find any way to pass this back in headers or response data on the initial connect flow.

And this stackoverflow post suggests that websockets simply doesn't support this.

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