WebSocket-for-Python icon indicating copy to clipboard operation
WebSocket-for-Python copied to clipboard

Implement a PEP3156 backend

Open Lawouach opened this issue 12 years ago • 8 comments

It'd be quite desirable that ws4py move on to a PEP3156 backend along its more traditional ones. This shouldn't not prevent regular CherryPy and gevent backends from existing indeed.

Lawouach avatar Sep 10 '13 18:09 Lawouach

Using the asyncio module available in PyPI for Python 3.3 and as a built-in in 3.4.

What to use for the HTTP parsing though?

Lawouach avatar Nov 25 '13 15:11 Lawouach

What does http://websockets.readthedocs.org/ use for HTTP parsing?

jodal avatar Nov 25 '13 15:11 jodal

Hey nice, I wasn't aware of that project :)

It seems they don't use any external dependencies. They perform their own parsing which may be enough.

Lawouach avatar Nov 25 '13 15:11 Lawouach

After browsing through other packages, it appears many of them already provide wbesockets atop asyncio. Im' starting to wonder if there is a point to support it from ws4py itself.

Lawouach avatar Jan 11 '14 13:01 Lawouach

Guess this can be closed now? :-)

jodal avatar Jan 14 '14 21:01 jodal

Yeah. Mostly. Though I would like to add client support as well. Shan't be long so it'll probably be done this week. But yai :)

Lawouach avatar Jan 14 '14 21:01 Lawouach

Can we still await AsyncIO Client WebSocket support or is this dead?

hilbix avatar Mar 08 '20 19:03 hilbix

Unfortunately, I've not maintained this project for years so I doubt it'll come. Always glad for the community to take over it though.

Lawouach avatar Mar 08 '20 20:03 Lawouach