You can purge the cache whenever you need and update it accordingly. You would then have a granular cache system ( or low-level cache ). You would have to update the cache whenever the object it self is updated...
Pretty common actually.. Victor Lima 2009/12/22 Continuation <selforgani...@gmail.com> > I looked at the doc and it seems that django's caching system is > based on time - you have to define how long a cached page or view will > live. > > For my case (and for a lot of people I'd imagine) that wouldn't work. > For example in generating an inox list list or "how many new messages > you have" count, I can't specify beforehand how long a cached element > will live - it will live as long as the underlying data has not been > updated. > > How do you handle situations like this? I guess what is needed is read- > through and write-through cache of individual objects. Is that > something that can be done with django? > > -- > > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
