On 7/20/07, John M <[EMAIL PROTECTED]> wrote: > > Does caching matter that much in my example, since it's dynamic data > anyway?
Don't let the fact that the data is dynamic distract you. All database backed websites are dynamic at some level. However, when you have thousands of requests for a resource every second, does it really matter if the version delivered to the user is 1 second out of date? 10 seconds? A minute? You should be able to serve a reasonably sized Django application without ever having to care about caching. However, It pays to get into a good habits early. It is a lot easier to add caching to the top of a clean ReSTful application than it is to refactor a messy, non-ReSTful application so that you can add caching. As a bonus, URL spaces that are easily cached are also the ones that match the browsing metaphor the best (i.e., are ReSTful), so asking the question "could I cache this" is one way of validating a design. 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 [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-users?hl=en -~----------~----~----~----~------~----~------~--~---
