On Wed, Oct 15, 2008 at 5:17 PM, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > Amit Upadhyay wrote: >> This is not about specs or what is allowed, rather what is there in >> actual django. And about implementation goals for django. It is >> possible to have a django(core+contrib apps shipped with django) with >> only SELECT queries in response for GET request. So far I have >> identified two places and their work arounds. Are there more? They >> should be avoided, and if not possible documented. > > For example you can't implement OpenID consumer without altering > application state on GET (actually logging a user in happens upon HTTP > redirect).
Its necessary given openid spec I guess. Can it be worked around by not splitting GET/POST for urls starting with /openid/? Can a GET on any request, thanks to some middleware maybe, write or writes are limited to one of few URLs? Such questions are not easy to answer offhand for someone who is using the app, and should be can go somewhere in readme.scaling.txt/less frequently asked question for the app may be. Along with other resources, files/directories etc that may be used by openid consumer, from the point of view of scaling. -- Amit Upadhyay Vakow! www.vakow.com +91-9820-295-512 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
