On Monday 21 January 2008 22:08:02 [EMAIL PROTECTED] wrote: > On Jan 21, 12:33 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > > - GET if you query information, not changing it (server side!) > > > > - POST if you change server side information > > > > And thus GET should be the default - or does each request of yours > > change your model? > > Diez > > Hmm. Yes whether the model (database) is changed is probably a good > test of whether a client side push to the server should be POST or > not. > > However, imagine a login/authentication system that kept the list of > authenticated users in a *session* object rather than the database. > That would imply the client send username/passwords to server with a > GET rather than a POST. But POST seems "right" in the login case > no? So not sure.
The question is not if there are corner-cases (there sure are, but your's would be a POST in my book), but why MK defaults to GET - and that is precisely because the majority of requests a browser does are queries, not updates/changes/whatsoever. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
