Re: [Web-SIG] Future of WSGI

2009-12-27 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Malthe Borch wrote: > > 2009/11/24 Ian Bicking : >> Why does this matter? > > It's all convention, but the CGI interpretation was to read the HTTP > request line by line until a blank line came and that was the > environment. Everything after that is

Re: [Web-SIG] Future of WSGI

2009-12-27 Thread Malthe Borch
2009/11/24 Henry Precheur : > (See http://tools.ietf.org/html/rfc2616#section-5) > > The request body, the request method (GET, POST, ...), the request URL, > the HTTP version are all in `environ`. That reference does not mention the environment. It's not an official term. > If you really want

Re: [Web-SIG] Future of WSGI

2009-12-27 Thread Henry Precheur
On Tue, Nov 24, 2009 at 10:50:00PM +0100, Malthe Borch wrote: > How people use or abuse software is not our concern; but the standard > library should not itself abuse its own abstractions. Your assumption is that `environ` == HTTP headers. That's simply NOT the case. A request is: - A reques

Re: [Web-SIG] Future of WSGI

2009-12-27 Thread Malthe Borch
2009/11/24 Ian Bicking : > Why does this matter? It's all convention, but the CGI interpretation was to read the HTTP request line by line until a blank line came and that was the environment. Everything after that is the body. If you want to obtain a shorter call signature – e.g. (environ, sta