durusmail: quixote-users: GET, POST, QUERY_STRING and FieldStorage
GET, POST, QUERY_STRING and FieldStorage
2003-03-22
2003-03-22
2003-03-25
Re: GET, POST, QUERY_STRING and FieldStorage
2003-03-25
2003-03-25
GET, POST, QUERY_STRING and FieldStorage
Neil Schemenauer
2003-03-25
On Mon, Mar 24, 2003 at 09:20:59PM -0500, Greg Ward wrote:
> On 21 March 2003, Jason Sibre said:
> > and a convenience accessor of:
> >
> > REQUEST[]
>
> No bloody way.  That's the first step on the road to Zope and the
> __getitem__() method from beyond the ninth circle of hell.  Also,
> conflating cookies and form data is (IMHO) a serious conceptual error.

I agree with your last sentence.  However, having __getitem__() call
get_form_var() might be convienient.  If you are not using the form
framework it gets pretty tedious to keep writing it out.

> They do not have the same purpose, and they should not be used for the
> same things.
>
> Here's a strawman API:
>
>   request.get_form_var('name')      # look in POST data, then GET data
>   request.form['name']              # ditto (maaaaaybe)

I don't think I like it.  I agree with Andrew that POST and GET data
should be kept separate.  It might be nice to make the GET data more
easily available if the form was POSTed.  Right now you have to get it
using get_environ("QUERY_STRING") and parse it yourself.  On the other
hand, I don't like to keep increasing the amount of work HTTPRequest
does for every request.  Maybe we could avoid that by parsing lazily.

  Neil

reply