I've updated this specification in response to input, mostly changing
language but not the meat of the specification itself:
http://wsgi.org/wsgi/Specifications/handling_post_forms
http://wsgi.org/wsgi/Specifications/handling_post_forms?action=diff
One thing that occurred to me is that wsgi.inpu
(Copied back to the list)
Andrew Clover wrote:
> Ian Bicking <[EMAIL PROTECTED]> wrote:
>
> > When this happens, the form can be parsed by ``cgi.FieldStorage``.
>
> Agree with the objections others have posted.
>
> There are many alternative things one might want to do with the body
> that do
Phillip J. Eby wrote:
Would you +1 the proposal if it is added that middleware does not
destroy
the wsgi.input variable but clones it?
>>> I didn't -1 the proposal, I -1'd middleware. And the -1 stands.
>>> Middleware is absolutely not the place for adding derivative environ
>>>
At 11:56 AM 10/24/2006 -0500, Ian Bicking wrote:
>That would be a landing place for an implementation of this library code
>that does what the spec implies. But it relies on the release cycle for
>wsgiref, which is unclear and probably very slow since it is in the stdlib.
Not really. wsgiref i
Phillip J. Eby wrote:
> At 12:25 PM 10/24/2006 +, Hans Then wrote:
>> Phillip,
>>
>>> -1 on this being middleware. If middleware wants to read the input,
>>> it should copy it to a temporary file or StringIO, not remove it.
>>> The simple, standard way to do something like this would be to hav
At 12:25 PM 10/24/2006 +, Hans Then wrote:
>Phillip,
>
> > -1 on this being middleware. If middleware wants to read the input,
> > it should copy it to a temporary file or StringIO, not remove it.
>
> > The simple, standard way to do something like this would be to have a
> > library routine l
Hans Then wrote:
> Phillip,
>
>> -1 on this being middleware. If middleware wants to read the input,
>> it should copy it to a temporary file or StringIO, not remove it.
>
>> The simple, standard way to do something like this would be to have a
>> library routine like 'get_form_vars(environ)'.
Phillip,
> -1 on this being middleware. If middleware wants to read the input,
> it should copy it to a temporary file or StringIO, not remove it.
> The simple, standard way to do something like this would be to have a
> library routine like 'get_form_vars(environ)'. The routine would
> check f
Phillip J. Eby wrote:
> At 02:04 PM 10/21/2006, Ian Bicking wrote:
>> I've added another spec to wsgi.org:
>> http://wsgi.org/wsgi/Specifications/handling_post_forms
>>
>> This one is a little more intrusive than wsgi.url_vars, but it addresses
>> an outstanding source of problems: contention over
At 02:04 PM 10/21/2006, Ian Bicking wrote:
>I've added another spec to wsgi.org:
>http://wsgi.org/wsgi/Specifications/handling_post_forms
>
>This one is a little more intrusive than wsgi.url_vars, but it addresses
>an outstanding source of problems: contention over wsgi.input.
-1 on this being mid
I've added another spec to wsgi.org:
http://wsgi.org/wsgi/Specifications/handling_post_forms
This one is a little more intrusive than wsgi.url_vars, but it addresses
an outstanding source of problems: contention over wsgi.input.
Text copied:
:Title: Handling POST forms in WSGI
:Author: Ian Bi
11 matches
Mail list logo
