Re: [Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Ian Bicking
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 >>>

Re: [Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Phillip J. Eby
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

Re: [Web-SIG] wsgi.url_vars feedback

2006-10-24 Thread Phillip J. Eby
At 05:39 PM 10/23/2006 -0500, Ian Bicking wrote: >By using a tuple or list, you can be sure you don't have a sparse list, >which probably isn't something any system is likely to handle. The >double underscores kind of mark __args__ as a special kind of key, so >it's less likely to overlap with a s

Re: [Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Ian Bicking
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

Re: [Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Phillip J. Eby
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

Re: [Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Ian Bicking
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)'.

[Web-SIG] Proposal: Handling POST forms in WSGI

2006-10-24 Thread Hans Then
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