Thanks Andy, I didn't know you could use a cache by name. That will be helpful.
On Feb 8, 9:22 pm, Andy McKay <a...@clearwind.ca> wrote: > You can define multiple caches: > > https://docs.djangoproject.com/en/1.3/topics/cache/#django-s-cache-fr... > > You could then use a file system cache or your own local memcache. > > https://docs.djangoproject.com/en/1.3/topics/cache/#filesystem-caching > > You can then get that cache and access it in your code: > > from django.core.cache import get_cache > cache = get_cache('my-filesystem-cache-defined-in-settings') > > > > > > > > On Wed, Feb 8, 2012 at 3:29 PM, bfrederi <brfrederi...@gmail.com> wrote: > > I'm already using memcached over http so I can have multiple memcached > > instances. But there isn't any way to set priority or which cache the > > item goes to or is pulled from. So if I had a local memcached > > instance, there's no way I could be sure which memcached instance the > > data was coming from. I already store the data on disk as a back-up in > > case the connection to my memcached servers fails. But I'm really > > looking to store it in local memory. And hopefully without adding any > > other tools to my stack. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
