Comment #1 on issue 9 by leidel: Save and remove signals doesn't take to account template sites http://code.google.com/p/django-dbtemplates/issues/detail?id=9
The SITE_ID settings defines which "Site" a Django process serves. Hence it's perfectly fine to let every Django instance create or remove the cache of a template itself. Passing the template object to the backend could solve that problem, yes. But you want to have as much separation between the different Django instances as possible, e.g. no interference between the cache operation of example.com and example.org. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pinax-updates" 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/pinax-updates?hl=en -~----------~----~----~----~------~----~------~--~---
