Remote cache expiration: 15 seconds.
远程缓存过期：15秒。
Remote cache expiration: 20 seconds.
远程缓存过期：20秒。
Remote cache expiration: 40 seconds.
远程缓存过期：40秒。
Remote cache expiration: 100 seconds.
远程缓存过期：100秒。
Step 2: Calculating remote cache expiration.
步骤2：计算远程缓存过期值。
Select an appropriate cache expiration policy.
选择一个适当的缓存过期策略。
Global default of remote cache expiration: 50 seconds.
远程缓存过期的全局缺省值：50秒。
Global maximum of remote cache expiration: 50 seconds.
远程缓存过期的全局最大值：50秒。
The cache expiration, and also the sweepers, work in an identical way.
缓存到期失效以及清理器的工作方式也应该相同。
Timed-cache expiration plug-in: Richard Livsey's plug-in to handle timed expiration of cache fragments.
基于时间的缓存过期插件：Richard Livsey的一款插件，可用来处理基于时间的缓存分段到期失效。
Public.expires — the cache expiration time (in seconds) for remote caches and for unauthenticated pages only.
expires——远程缓存的缓存过期时间(以秒为单位)，只针对未经身份验证的用户。
As mentioned earlier, there is a special mechanism for portlets for the contributed value of the cache expiration.
正如前面所提到的，对于Portlet有一个特殊的机制处理提供的缓存过期值。
Listing 5 shows a fragment of a standard portlet that publishes the cache expiration time and cache scope at render time.
清单5显示了在呈现时发布缓存过期时间和缓存作用域的标准Portlet的片段。
The general idea for the calculation is to use the minimum for both cache scope and cache expiration time to make sure that.
计算过程通常就是对缓存作用域和缓存过期时间均使用最小值，以确保以下事项。
You can reduce HTTP requests by providing HTTP cache expiration headers with future dates that allow browsers to cache components.
可以提供指定了未来日期的HTTP缓存过期头，这会让浏览器对组件进行缓存，因此可以减少HTTP请求。
The JSR 168 specification defines a general cache expiration time value that a portlet may set itself at any time during rendering.
JSR 168规范定义了一个通用缓存过期时间值，Portlet可以在呈现期间随时自行进行设置。
In the second step, WebSphere Portal calculates the minimum of the remote cache expiration of the information contributed by all of the components.
在第二步中，WebSpherePortal将计算所有组件提供的信息的远程缓存过期最小值。
Some of the important fields of this structure are the interface specification name service cache expiration age to know if the cache has to be refreshed.
这个结构中的重要字段包括接口规范名称服务缓存过期时间，这用于确认是否必须刷新缓存。
To make sure that a portal page is not cached in a remote cache, the cache expiration either for the portal page or globally for the portal needs to be set to 0.
为了确保不在远程缓存中缓存门户页面，需要将该门户页面的缓存过期值或全局范围内的对应值设置为 0。
Since there is no need to distinguish internal and remote cache expiration values, WebSphere Portal USES this as the contributing value of this portlet definition for remote caching.
由于没有必要区分内部缓存过期值和远程缓存过期值，WebSpherePortal会将此作为该Portlet定义为远程缓存定义的提供值使用。
If no value for either cache expiration or cache scope is contributed by the portlet window, the value from the portlet definition will then be used as the contributing value of the portlet.
如果Portlet窗口没有为缓存过期或缓存作用域提供值，则会将Portlet定义中的值作为该Portlet的提供值。
If the cache is full, the first entry to be evicted from the cache is the entry that is closest to expiration.
如果缓存已满，那么从缓存中移除的第一个条目是距到期日期最近的缓存条目。
As you cache pages that are substantially more dynamic, the expiration logic will get more complicated.
由于想要缓存的页面高度动态，所以到期失效逻辑就会变得更加复杂。
The lifecycle of a cache item is governed by local policy and response expiration.
缓存中条目的生命周期取决于本地策略和响应的到期时间。
Each cache type can have a different expiration period setup.
每种类型的高速缓存都可以配置不同的到期时间。
To cause a page to be added to the output cache, you establish an expiration policy for that page.
当将页添加到输出缓存后，在超过了您在到期策略中指定的时间量之后，该页将被移除。
Secondly, the Cache supports expiration dependencies that can force invalidation.
第二，缓存支持可以强制失效的过期依赖项。
While the minimum of several expiration time values is easy to determine, the minimum of two possible cache scope values is less obvious.
很容易确定若干个过期值中的最小值，而两个可能的缓存作用域最小值却不是那么明显。
Remember that if you use far future expiration dates, browsers will still cache your content even when you have changed it.
请记住，如果把过期日期设置为很长时间以后，那么即使已经修改了内容，浏览器仍然会使用缓存的内容。
This approach may not be beneficial when information is highly dynamic, as the expiration of the cache may introduce overhead that defeats a cache's intended purpose..
当信息高度动态时，这种方法也许无益，因为缓存引入的开销可能挫败缓存的预期目的。
应用推荐