From 8f3a3c5544401c2e69f7354644420258caa4e8c2 Mon Sep 17 00:00:00 2001 From: Aditya Chadha Date: Sat, 2 May 2009 18:36:13 -0400 Subject: Formatting fixes, take 2 --- railties/guides/source/caching_with_rails.textile | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) (limited to 'railties/guides/source/caching_with_rails.textile') diff --git a/railties/guides/source/caching_with_rails.textile b/railties/guides/source/caching_with_rails.textile index d38d3a9949..9fd8b8a1fe 100644 --- a/railties/guides/source/caching_with_rails.textile +++ b/railties/guides/source/caching_with_rails.textile @@ -360,21 +360,14 @@ most popular cache store for production websites. Special features: -* Clustering and load balancing. One can specify multiple memcached servers, - and MemCacheStore will load balance between all available servers. If a - server goes down, then MemCacheStore will ignore it until it goes back - online. - +* Clustering and load balancing. One can specify multiple memcached servers, and MemCacheStore will load balance between all available servers. If a server goes down, then MemCacheStore will ignore it until it goes back online. * Time-based expiry support. See +write+ and the +:expires_in+ option. - * Per-request in memory cache for all communication with the MemCache server(s). It also accepts a hash of additional options: * +:namespace+- specifies a string that will automatically be prepended to keys when accessing the memcached store. - * +:readonly+- a boolean value that when set to true will make the store read-only, with an error raised on any attempt to write. - * +:multithread+ - a boolean value that adds thread safety to read/write operations - it is unlikely you'll need to use this option as the Rails threadsafe! method offers the same functionality. The read and write methods of the MemCacheStore accept an options hash too. -- cgit v1.2.3