Malcolm: We have currently implemented a Middleware Hack to alter the settings.SITE_ID
The problem being that our project is serving more then 10 domain names and we are aiming at about 1200 requests/second. We don't want to hesitate when the load gets high, to through another App Server to handle the traffic. I am wondering how this exactly affects the caching? Shouldn't the caching be getting and setting based off of settings.SITE_ID? Your post scares me and makes me want to dig through all the Django Caching code to see how exactly it will break. Maybe we will be the first to patch the breakage as it doesn't seem like it should break to me. Any clarification would be helpful. Jimmy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
