Malcom, Great suggestion. I'll do just that. It shouldn't be too hard and I will have to write a script to update server numbers anyway. I'll be sure to write about it when its complete.
Also, thanks to everyone else who posted. On Mar 9, 11:42 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Mon, 2009-03-09 at 21:28 -0700, Dave Fowler wrote: > > Thanks. So to summarize, > > > No one knows of a way to change memcached settings without having to > > re-load the django settings > > They're not intended to be changed like that, which is why you haven't > been flooded with answers. Not a matter of not knowing, so much as > "don't do that." The basic rule is "don't change settings after they're > set", since the code does a bunch of assuming they won't change in > general. > > [...] > > > Any other solutions? > > Django supports pluggable cache backends for cases like this. Write a > backend that uses most of the existing memcached backend (it's nicely > subclassable), but looks up the servers to connect to by some other > means. Perhaps reading from a file on disk every N requests or something > like that. I strongly suspect that wouldn't be that much work to > implement. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
