We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After reading RFC 6455 and reviewing the code I think that we can make it better in couple ways:
RFC mentions 4 states of connection
Current implementation has
I think we can move to RFC convention, which makes sense: one, from architectural pov; two, it would follow official specification.
Couple of loose thoughts here:
A lot. WIth nicely divided code base that should show lots of bugs, unusual behaviours etc. Adding Proper here would be nice to cover all that.
Thoughts on that?
ps.: + extensions
The text was updated successfully, but these errors were encountered:
Completely agree on all counts!
Sorry, something went wrong.
No branches or pull requests
After reading RFC 6455 and reviewing the code I think that we can make it better in couple ways:
Naming
RFC mentions 4 states of connection
Current implementation has
I think we can move to RFC convention, which makes sense: one, from architectural pov; two, it would follow official specification.
Reshape the code base (little bit ;) )
Couple of loose thoughts here:
Add tests
A lot. WIth nicely divided code base that should show lots of bugs, unusual behaviours etc. Adding Proper here would be nice to cover all that.
Thoughts on that?
ps.: + extensions
The text was updated successfully, but these errors were encountered: