处理缓存页面和页面碎片效果最好。
在默认情况下，只借出文件缓存页面。
打开其中一个来看一下缓存页面的样子。
Open one up and have a look at what the cached page looks like.
Google的缓存页面就是典型的用例。
它妨碍了站点的性能，因为不能缓存页面来供不同的用户使用。
It interferes with the performance of the site because the pages cannot be cached and reused for different users.
一旦你的请求被处理，我们将从搜索结果中删除网页摘要和缓存页面。
Once your request has been processed, we'll remove the snippet and the cached page from search results.
对于DMS设备容器表空间，操作系统不在文件系统缓存器中缓存页面。
For DMS device container tablespaces, the operating system does not cache pages in the file system cache.
此方法的工作方式与缓存动作和缓存页面的到期失效是一样的。
This method works just like the expiration of cached actions and pages.
对于已缓存页面的请求再无需通过从浏览器到后端系统的整个基础设施了。
Requests to cached pages do not need to cross the entire infrastructure from the browser to the backend system.
这是必要的，原因就包括Tapestry如何处理在请求间缓存页面。
This is necessary for a number of reasons, including to address how Tapestry pools pages between requests.
这可以在文件数据被复制到内部缓存区时立即释放用于保留该数据的NFS缓存页面。
This frees up NFS cache pages used to hold file data as soon as they have been copied to internal buffers.
借助部分缓存，可以缓存页面的一部分，所缓存的内容很多时候都是布局之类的。
Using partial caching, you can cache a portion of a page, often the content for a layout.
在该页面被重新抓取和索引之后，搜索结果及更新后的摘要及缓存页面(基于新内容)将可见。
After the page has been re-crawled and re-indexed, the search result with an updated snippet and cached page (based on the new content) can be visible.
多数定制清理器都会观察某些模型对象，并根据更改击发逻辑来使一个或多个缓存页面到期失效。
Most custom sweepers observe some model object, and based on changes, fire logic to expire one or more cache pages.
在优化查询和缓存页面这两个选项当中，如果您能“消受”复杂性，缓存页面将会带来更大的回报。
Given a choice between optimizing a query and caching a page, caching the page will give you a far greater return, if you can stomach the complexity.
为了在这些区域中提供缓存页面，对页面的请求必须来自已经使用相同的URL访问该页面的用户。
In order to serve a cached page in these areas, the request for the page must come from a user who already accessed the page using that exact URL.
这个头也可以防止使用后退按钮时访问了缓存页面,它将触发一个HTTPGET请求.
This header also prevents reuse of the cached version of the page and triggers an HTTP GET if the page is navigated to using the Back button.
繁忙的Drupal站点可以考虑缓存页面，从而减轻服务器的负载并加快生成页面的速度。
Busy Drupal sites may consider caching their pages to lighten the load on their server and speed up page-generation times.
在这里，我将把PHP与名为反向代理(reverse proxy)的智能软件结合使用来缓存页面和节省服务器。
Here, I combine PHP with smart software called a reverse proxy to cache pages and save servers.
只有在可以计算附加的缓存信息(此信息随webspherePortal服务器响应一起发送)的情况下，这两种缓存才能成功地缓存页面。
Both kinds of caches can successfully cache pages only if they are able to evaluate additional cache information that is sent along with the WebSphere Portal server response.
利用此功能，也可以通过URL从缓存中访问已缓存的页面。
With this feature, cached pages can be accessed from the cache also via the URL.
为了处理页面缓存，我必须先解决所有的差异。
In order to handle page caching, I must deal with all of the differences.
缓存后的页面和动作都会进入公共目录。
并不是每个网站都能使用页面缓存。
由于想要缓存的页面高度动态，所以到期失效逻辑就会变得更加复杂。
As you cache pages that are substantially more dynamic, the expiration logic will get more complicated.
静态页面缓存。
不过会缓存该页面上的图像。
如果想要基于应用程序内的条件—例如，身份认证—来缓存整个页面，那么可以使用动作缓存。
If you need to do whole page caching based on conditions in the application - authentication, for example - you can use action caching instead.
从图1可以看到一个博客站点内可被缓存的页面分区。
You can see in Figure 1 some of the page fragments within a blog that could be cached.
从图1可以看到一个博客站点内可被缓存的页面分区。
You can see in Figure 1 some of the page fragments within a blog that could be cached.
应用推荐