From 2822f71d08f3a94a3e26bb80fa1dbcef7bf2f1db Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Sat, 29 Oct 2005 17:05:19 +0000 Subject: Fixed #140: memcached backends may now use multiple servers git-svn-id: http://code.djangoproject.com/svn/django/trunk@1021 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- django/core/cache.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'django/core/cache.py') diff --git a/django/core/cache.py b/django/core/cache.py index 6391304158..caeb315f05 100644 --- a/django/core/cache.py +++ b/django/core/cache.py @@ -13,7 +13,9 @@ settings.CACHE_BACKEND and use that to create and load a cache object. The CACHE_BACKEND setting is a quasi-URI; examples are: memcached://127.0.0.1:11211/ A memcached backend; the server is running - on localhost port 11211. + on localhost port 11211. You can use + multiple memcached servers by separating + them with semicolons. db://tablename/ A database backend in a table named "tablename". This table should be created @@ -134,7 +136,7 @@ else: "Memcached cache backend." def __init__(self, server, params): _Cache.__init__(self, params) - self._cache = memcache.Client([server]) + self._cache = memcache.Client(server.split(';')) def get(self, key, default=None): val = self._cache.get(key) -- cgit v1.3