On Friday 31 March 2006 18:51, oggie rob wrote: > Should this decorator be added to the generic views? I can see > arguments either way. Perhaps it is safer to come up with a different > generic view (or a parameter) if you never want to cache?
I think it should be added to create/update, because the data loss scenario I outlined above is relevant there. For others, Django aims to be 'cache friendly' out of the box, and we don't want to change that. Perhaps it would be good to have some parameter to control max age/expiration on those views. What do the core devs think? Luke -- A woman's mind is cleaner than a man's. She changes it more often. (Oliver Herford) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
