On 6/19/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > > > Which cache backend are you using? The snippet I linked is for *a* > > backend. Many of the Django caching backends do need to pickle since > > they marshal out of process. > > Um, "The django cache" implies there is only one. There may have been other > stuff and I hate to be hostel about it, but I have no motivation to go digging > up something that you trimmed.
There is only one django.core.cache, but there are many backends, depending on settings.CACHE_BACKEND. http://www.djangoproject.com/documentation/cache/#setting-up-the-cache http://www.djangoproject.com/documentation/settings/#cache-backend There's no need to be hostile, I'm just trying to thoroughly answer your question. When it comes time to deploy, you may use a cache backend that has a different implementation and has the performance issue you're trying to avoid. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
