Add functions to allow proper subclassing of WebSocket*Protocol about websockets

[aaugustin]

I'm really sorry, but I don't get what changes you're asking for.

Here's an example of subclassing WebSocketServerProtocol:
https://github.com/aaugustin/websockets/blob/master/compliance/test_server.py#L11-L20

If that doesn't answer your question, maybe you could show me what you're trying to do, what results you get, and explain what results you would expect?

Otherwise, is this an issue with the documentation?

Thanks!

[aaugustin]

Just after writing that comment, I noticed DCP-Project/minnow-prototype@1153086#diff-017639d70cd2c855d3f7c4ed46c3b2c2R362.

If I understand correctly, you would like to be able to handle incoming websocket messages through callbacks rather than by defining a handler.

Considering the design of the API and the current implementation, this is rather hard. I would need an incremental parser, which I haven't implemented. Writing everything with coroutines makes the code much simpler (as you might expect — that's pretty much the point of asyncio).

Choosing coroutines over callbacks was an early design decision of the project. Later I realized it would prevent some use cases, but that's the way I wanted to write it and it don't see any useful way to refactor it.

Your best chance is to write a websocket handler that reads messages in a loop and calls the callback whenever it gets a message, which is what you did. I don't understand entirely why you have so much code around, because I don't know the context, but that was the right idea if you want to use my library.

Maybe you should use another library, there's a few hanging around.