Amit Upadhyay wrote: > 1. make sure none of your apps do db writes on GET. [It was the case > with my entire project already, other than one case, which was trivial > to work around]. > 2. Use non db session backend. > 3. Not use auth messages. [This presented some problems for me, but I > had luckily using wrapper for message creation and not > User.message_set.create() as recommended in docs; after porting > http://code.djangoproject.com/ticket/4604 to my django-0.96, all I had > to do was to change few lines here and there]. > > And you have a safe "pure systems where GET doesn't touch any state", > which is not complex and I use it at my website!
First, what you describe doesn't touch DB but it does alter state. If you keep your sessions in different storage it doesn't mean that you can write to it and still consider it "pure". And second, it's not "not complex" because of your item 1: "make sure none of your apps do db writes". The fact that you could achieve it with your application doesn't automagically solve this for everyone else. You are trying to show that "pure GETs" is a simple matter of patching Django in a couple of places. But it's not because Django itself has nothing to do with it. It's user's code that matters and in most cases people have many good engineering reasons to implement parts of their systems with some deviations from REST. I don't understand how simply ensuring absence of DB writes on GETs is going to solve this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
