kotovalexarian-likes-github
/
sinatra
mirror of https://github.com/sinatra/sinatra
1
0
Fork 0
Code Releases Activity

Slight changes to wording regarding caching.

This commit is contained in:
Tim Preston 2011-08-20 14:37:16 +10:00
parent f1b35074c5
commit 8d5fd6adf4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rdoc
View File

@ -980,7 +980,7 @@ If you are using the +expires+ helper to set the corresponding header,
expires 500, :public, :must_revalidate expires 500, :public, :must_revalidate
end end
To properly use caches, you should consider using +etag+ and +last_modified+. To properly use caches, you should consider using +etag+ or +last_modified+.
It is recommended to call those helpers *before* doing heavy lifting, as they It is recommended to call those helpers *before* doing heavy lifting, as they
will immediately flush a response if the client already has the current will immediately flush a response if the client already has the current
version in its cache: version in its cache:
@ -998,7 +998,7 @@ It is also possible to use a
etag @article.sha1, :weak etag @article.sha1, :weak
These helpers will not do any caching for you, but rather feed the necessary These helpers will not do any caching for you, but rather feed the necessary
information to your cache. If you are looking for a quick caching solutions, information to your cache. If you are looking for a quick reverse-proxy caching solution,
try {rack-cache}[http://rtomayko.github.com/rack-cache/]: try {rack-cache}[http://rtomayko.github.com/rack-cache/]:
require "rack/cache" require "rack/cache"