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

WebSocket #20

Closed
marconi opened this issue Feb 1, 2013 · 4 comments
Closed

WebSocket #20

marconi opened this issue Feb 1, 2013 · 4 comments

Comments

@marconi
Copy link

marconi commented Feb 1, 2013

Is the WebSocket middleware stable for production use and web socket spec. compliant?
@andrew-d
Copy link

I'd also be interested in knowing this.

@mopemope
Copy link
Owner

Meinheld Websocket middleware is unstable yet...
(It is fork Eventlet websocket.)
It isupports only "RFC6455".

@ricardo-kagawa
Copy link
Contributor

I am interested in this feature. Can I help?

For instance, I could try adding Autobahn's test suite for WebSockets, which seems to be considered a standard of sorts. Are you interested?

But I am really new to contributing to open source. Should I just submit a pull request, or should I ask you some directions before?

@methane
Copy link
Collaborator

methane commented Sep 23, 2014

@ricardo-kagawa Feel free to create pull request.
Add test for new feature and run it on Travis-CI if possible.

ricardo-kagawa added a commit to ricardo-kagawa/meinheld that referenced this issue Nov 22, 2014
@ricardo-kagawa
Responses with status "101 Switching Protocols" send "Connection: upg…
d33edc5 
…rade" instead of "close" or "keep-alive" (refs mopemope#20).
@methane methane closed this as completed Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mopemope @marconi @methane @andrew-d @ricardo-kagawa