In the case of simple portlets, fragment caching should not be enabled.
对于简单Portlet，不应启用片断缓存。
So far, I've discussed page and fragment caching models for Ruby on Rails.
至此为止，我已经介绍了Ruby on Rails的页面和分段缓存模型。
In the previous sections, you learned how to enable portlet fragment caching.
在前面的部分中，您已了解如何启用Portlet片段缓存。
Select the check box for enabling portlet fragment caching as shown in Figure 1.
选中用于启用Portlet片段缓存的复选框，如图1所示。
Both page and fragment caching occur at the controller level. You need to tell rails.
页面和分段缓存二者均在控制器级别发生。
In the command prompt, you enter the following commands to enable portlet fragment caching.
在命令提示符中，输入下列命令以启用Portlet片段缓存。
Another way you can turn on portlet fragment caching is by using the scripting interface, wsadmin.
可启用Portlet片段缓存的另一种方法是：通过使用脚本编程接口wsadmin。
This support is an extension of the servlet fragment caching with a few additional options. Part 3.
此支持是Servlet片段缓存的扩展，具有一些额外的选项。
Beside readable code we introduced a simple caching similar to the fragment caching found in Rails views.
除了我们介绍的高易读性的代码，我们还介绍了一种简单的，类似于Rails视图中使用的碎片缓存的缓存技术。
You can live within the constraints of the Rails framework, striking page caching to use fragment caching instead.
在Rails框架的约束之内，取消页面缓存并使用段缓存替代它。
This section shows how you can turn on portlet fragment caching using the administrative console or with the scripting interface.
此部分说明如何使用管理控制台或脚本编程接口来启用Portlet片段缓存。
We don't use action caching for many of the same reasons we don't use page caching, but fragment caching is much more important for us.
我们不使用动作缓存的原因与我们不使用页面缓存的原因是一样的，但分段缓存对我们来说更重要一些。
For ChangingThePresent.org, we primarily use fragment caching, and we invalidate caching fragments from the controller, primarily using a time-based method.
对于ChangingThePresent.org，我们主要使用分段缓存，并通过控制器使用基于时间的方法来使缓存分段到期失效。
However, WebSphere application Server provides support for page and fragment caching through its dynamic cache function without requiring any application changes.
然而，WebSphere提供了对页面以及片断缓存的支持，这种支持是通过其动态缓存功能来实现的，并且不需要对应用程序作出任何改变。
You can configure portlet fragment caching more precisely in both environments, but these extensions are portal specific and are different in WebSphere portal and WebSphere Application Server.
您可以在两种环境中更精确地配置Portlet片段缓存，但是这些扩展是特定于门户的，并且在WebSpherePortal和WebSphereApplication Server中有所区别。
In this section, we will explain how WebSphere Portal exploits the fragment cache to cache individual portlet fragments (see Example application for portlet caching).
在这一部分中，我们将说明WebSpherePortal如何利用片段缓存来缓存单个Portlet片段(请参阅Portlet缓存示例应用程序)。
Caching effectiveness - analysis and reporting on both fragment and page caching.
缓存有效性——分析及报告片段和页面缓存。
Caching effectiveness - analysis and reporting on both fragment and page caching.
缓存有效性——分析及报告片段和页面缓存。
应用推荐