Marty Alchin wrote: > Regardless though, I think Jacob makes the best point so far: Django's > cache system is robust enough to handle it if you pick a decent > backend. And if there's a need to make the built-in options more > robust, we can deal with that when the need arises. > What about registering to watch for a signal given to the web server process and invalidate the cache when that is received ? That way someone who really wants to clear the dbsettings across multiple processes can force it via a "kill -s" system script.
Just an idea, Rob :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
