On Jan 21, 2008 4:08 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 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. >From the client's point of view, the exact _location_ of the state data is irrelevant--it's all server-side state. A HTTP client doesn't know database from in-memory object from flat files on a 3.5" floppy. Aside from some real corner cases, the decision process is usually straightforward: http://www.w3.org/2001/tag/doc/whenToUseGet.html#checklist -- Tim Lesher <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
