disclaimer: i'm in no way opposing the deprecation of request.REQUEST. still, i feel there are lots of bad reasons in PHP-land about discouraging use of that feature (typically some imagined security reasons). I'd like to see some good reasons besides aesthetics (yes, it's ugly) and duplication of functionality.
On Wed, Oct 16, 2013 at 11:29 AM, Tim Chase <django.us...@tim.thechases.com> wrote: > On 2013-10-16 11:10, Javier Guerra Giraldez wrote: >> On Wed, Oct 16, 2013 at 10:14 AM, Shai Berger <s...@platonix.com> >> wrote: >> > However, it does so by blurring the distinction between GET and >> > POST parameters, which like other people here, I find >> > disturbing. >> >> care to elaborate about that distinction? both are user-provided >> parameters included in the request. the only difference i see is >> about encoding. > > Because they're sent different ways. POST variables in the request > body, and GET parameters are in the URL. same origin: the browser or any http client same destination: the web app same transport: the http request encoded in different parts of the request (body vs url). yes, they're different, but is there any value in emphasizing the difference? -- Javier -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFkDaoRgoDbLr4WEc43w%3DRc8yBMG%2B66LDkMFx_F95vJQyLELGw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
