that's what we are trying and discussing about: if the get(post)_vars should depend on GET and POST request method or if they are aliases for "parsed_query_string" (get_vars) and "parsed_body_string" (post_vars).
The fact is, in the 90% of the cases they practically overlap. Most of the users are using request.vars unconditionally, so less and less code will eventually brake. But we need to make a decision and live with the consequences ^_^ (I'm hearing right now the next blogpost saying "web2py's shitty naming convention for variables...") On Thursday, August 22, 2013 11:55:58 PM UTC+2, Tim Richardson wrote: > > > Here's the catch: in CGI there are multiple ways to submit params in a >> POST request: >> - with the "query string" >> - with body holding the "query string" (application/x-www-form-urlencoded) >> - with body holding a mime format (multipart/form-data) >> > > Thanks. I didn't know that: I thought query string and GET were in an > exclusive relationship. > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
