On 7/21/07, John Matthew <[EMAIL PROTECTED]> wrote: > Given that, I assume that the cache will look at the http://.../model3/add/ > and cache that? meaning it doesn't add the parameters to the cache lookup?
Ultimately it will depend on your caching mechanism, but in theory, any page that has been retrieved with GET should be cacheable, without consequence, parameters and all. GET is intended to be a resource retrieval, and if you're just retrieving, you're not modifying the server, so it should be cachable. Remember, the object isn't created until you POST the data, and it's the POST that can't be cached. Caching the GET ..model3/add/?model1=2 page just means that the unsubmitted form with a hinted value for model1 has been cached, ready for the next person that wants to add an instance of model3 with the same hinted value. > Thanks again for all your help. No problems. Happy to help. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
