[issue13354] tcpserver should document non-threaded long-living connections

Bas Wijnen added the comment: Thank you for your fast response as well. I overlooked that paragraph indeed. It doesn't mention anything about avoiding a socket shutdown however. Keeping a list of requests isn't very useful if all the sockets in the list are closed. ;-) So I would indeed

[issue13354] tcpserver should document non-threaded long-living connections

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue13354] tcpserver should document non-threaded long-living connections

Martin Panter added the comment: Thanks for the fast response! There is a paragraph right at the end of that mentions this technique: “. . . maintain an explicit table of partially finished requests . . .”. Perhaps

[issue13354] tcpserver should document non-threaded long-living connections

Bas Wijnen added the comment: For example, I have some programs which are HTTP servers that implement WebSockets. For regular web page requests, it is acceptable if the connection is closed after the page is sent. But for a WebSocket it isn't: the whole point of that protocol is to allow

[issue13354] tcpserver should document non-threaded long-living connections

Martin Panter added the comment: Bas: I think you need to provide more information. Are you talking about protocols like HTTP, where multiple high-level (HTTP-level) requests are made over a single low-level (socket-level) connection? Some example code might help. Overriding

[issue13354] tcpserver should document non-threaded long-living connections

Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13354 ___ ___ Python-bugs-list

[issue13354] tcpserver should document non-threaded long-living connections

Mark Lawrence added the comment: Am I barking up the wrong tree, or should the docs now refer to the new asyncio module aka Tulip when mentioning asynchronous behaviour? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org

[issue13354] tcpserver should document non-threaded long-living connections

New submission from Bas Wijnen wij...@debian.org: http://docs.python.org/py3k/library/socketserver.html says: The solution is to create a separate process or thread to handle each request; the ForkingMixIn and ThreadingMixIn mix-in classes can be used to support asynchronous behaviour. There