Re: [Web-SIG] ANN: General availability of the WebCore WSGI nanoframework v2.0.

2016-04-19 Thread Marcel Hellkamp
Currently, all the links in this mail are dead. Am 19.04.2016 um 00:17 schrieb Alice Bevan–McGregor: Best Practices Morpheus says: "What if I told you things can get simpler, more independent, and more testable, with a separation of concerns in a glorious holy land?" WebCore is a WSGI nanofra

Re: [Web-SIG] websocket support in WSGI

2012-05-21 Thread Marcel Hellkamp
Am 21.05.2012 15:47, schrieb Simon Sapin: > Le 21/05/2012 14:36, Alex Grönholm a écrit : >> This has been discussed before and it's impossible to implement since >> proxying such things does not work over a number of protocols (FCGI, >> SCGI). IIRC, the front-end web server likes to send its own 1x

[Web-SIG] Most WSGI servers close connections to early.

2010-09-22 Thread Marcel Hellkamp
issue: "An application should read all available data from `environ['wsgi.input']` on POST or PUT requests, even if it does not process that data. Otherwise, the client might fail to complete the request and not display the response." -- Mit freundlichen Grüßen Marcel Hellkamp _

Re: [Web-SIG] PEP 444 (aka Web3)

2010-09-18 Thread Marcel Hellkamp
art_response callable is inconvenient for middleware to implement, but it totally made sense. -- Mit freundlichen Grüßen Marcel Hellkamp ___ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org