diff options
author | Aditya Chadha <aditya@sublucid.com> | 2009-02-23 01:35:15 -0500 |
---|---|---|
committer | Aditya Chadha <aditya@sublucid.com> | 2009-02-23 01:35:15 -0500 |
commit | 8aec73304835e09fdeed903a5ad6ffe8105194fd (patch) | |
tree | de7b529641d89ee25f365ec2ca00d2ddb9e303bd | |
parent | 77aa8a6b815db56c530ef5270e4cd386940befac (diff) | |
download | rails-8aec73304835e09fdeed903a5ad6ffe8105194fd.tar.gz rails-8aec73304835e09fdeed903a5ad6ffe8105194fd.tar.bz2 rails-8aec73304835e09fdeed903a5ad6ffe8105194fd.zip |
More special character removal and added cache_money to the reference list
-rw-r--r-- | railties/guides/source/caching_with_rails.textile | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/railties/guides/source/caching_with_rails.textile b/railties/guides/source/caching_with_rails.textile index cbe15689c1..56d4653090 100644 --- a/railties/guides/source/caching_with_rails.textile +++ b/railties/guides/source/caching_with_rails.textile @@ -318,7 +318,7 @@ The default cache stores provided include: everything into memory in the same process. If you're running multiple Ruby on Rails server processes (which is the case if you're using mongrel_cluster or Phusion Passenger), then this means that your Rails server process instances -won‘t be able to share cache data with each other. If your application never +won't be able to share cache data with each other. If your application never performs manual cache item expiry (e.g. when you‘re using generational cache keys), then using +MemoryStore+ is ok. Otherwise, consider carefully whether you should be using this cache store. @@ -490,13 +490,14 @@ h3. Advanced Caching Along with the built-in mechanisms outlined above, a number of excellent plugins exist to help with finer grained control over caching. These include -Chris Wanstrath's excellent cache_fu plugin (more info here: -http://errtheblog.com/posts/57-kickin-ass-w-cachefu) and Evan Weaver's -interlock plugin (more info here: -http://blog.evanweaver.com/articles/2007/12/13/better-rails-caching/). Both +Chris Wanstrath's excellent cache_fu plugin (more info "here": http://errtheblog.com/posts/57-kickin-ass-w-cachefu) and Evan Weaver's +interlock plugin (more info "here": http://blog.evanweaver.com/articles/2007/12/13/better-rails-caching/). Both of these plugins play nice with memcached and are a must-see for anyone seriously considering optimizing their caching needs. +Also the new "Cache money":http://github.com/nkallen/cache-money/tree/master plugin is supposed to be mad cool. + + h3. Changelog "Lighthouse ticket":http://rails.lighthouseapp.com/projects/16213-rails-guides/tickets/10-guide-to-caching |