From d8ef5b0e6501692b8b767ebccddc936f496d77e8 Mon Sep 17 00:00:00 2001 From: Ed Morley Date: Wed, 31 Aug 2016 18:15:22 +0100 Subject: Fixed #27152 -- Supported comma delimiter in memcached LOCATION string. --- docs/releases/1.11.txt | 4 ++++ docs/topics/cache.txt | 9 +++++++-- 2 files changed, 11 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/releases/1.11.txt b/docs/releases/1.11.txt index d6a59c8ab9..3f232a56b8 100644 --- a/docs/releases/1.11.txt +++ b/docs/releases/1.11.txt @@ -173,6 +173,10 @@ Cache control of client behavior. See the :ref:`cache arguments ` documentation for examples. +* Memcached backends now allow defining multiple servers as a comma-delimited + string in :setting:`LOCATION `, for convenience with + third-party services that use such strings in environment variables. + CSRF ~~~~ diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 1730ef6294..2a48a66abe 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -128,8 +128,8 @@ multiple servers. This means you can run Memcached daemons on multiple machines, and the program will treat the group of machines as a *single* cache, without the need to duplicate cache values on each machine. To take advantage of this feature, include all server addresses in -:setting:`LOCATION `, either separated by semicolons or as -a list. +:setting:`LOCATION `, either as a semicolon or comma +delimited string, or as a list. In this example, the cache is shared over Memcached instances running on IP address 172.19.26.240 and 172.19.26.242, both on port 11211:: @@ -168,6 +168,11 @@ permanent storage -- they're all intended to be solutions for caching, not storage -- but we point this out here because memory-based caching is particularly temporary. +.. versionchanged:: 1.11 + + The :setting:`LOCATION ` setting now supports defining + multiple servers as a comma-delimited string. + .. _database-caching: Database caching -- cgit v1.3