缓存控制器执行的所有操作。
您可能希望缓存控制器执行的所有操作。
动作缓存让您能够利用认证及控制器上的任何过滤器。
Action caching lets you take advantage of authentication and any filters on the controller.
将这些信息放在前端总线中看，请求代理人让其他的处理器知道这种执行是如何影响缓存以及存储控制器(北桥)是如何运转的。
By putting this information on the FSB, the request agent lets other processors know how this transaction affects their caches, and how the memory controller (northbridge) should behave.
在某些控制器击发时，这些类会从缓存内删除选定的元素。
These classes delete selected elements from your cache when certain controller actions fire.
缓存能在控制器级别配置，最终是利用了ASP.NET的缓存基础功能。
Cache can be configured on the controller level, and ultimately USES the ASP.NET caching infrastructure.
您可以通过指定产品控制器对view操作使用缓存来测试这段代码。
You can test this out by specifying that the products controller uses caching for the view action.
对Catalog控制器的根本更改是，从遗留 Catalog 实现更改到了缓存代理，如下所示
The fundamental change to the catalog controller was changing to cached proxy from the legacy catalog implementation, as follows
例如，如果需要缓存产品视图，则必须在产品控制器的helpers数组中包含Cache。
For example, to cache the products views, you would have to include cache in the helpers array for the products controller.
页面和分段缓存二者均在控制器级别发生。
Both page and fragment caching occur at the controller level. You need to tell rails.
我也可以选择在rhtml页面中指定超时和缓存方法，但我更愿意使用基于控制器的方法。
I could have also chosen to specify the timeout within the RHTML page along with the cache method, but we prefer the controller-based method.
对于每个被缓存的元素，只需指定想要缓存的内容、可生成动态内容的任何控制器动作以及超时。
For each cached element, you need only specify the content you want to cache, any controller action that produces your dynamic content, and a timeout.
一旦收到此事件，控制器就会知道提要数据是在模型对象中缓存并可在视图中展示。
Upon receiving this event, the controller knows that the feed data is cached in the model object and can be presented in the view.
Catalog控制器将始终首先访问缓存代理。
The catalog controller always accesses the cache proxy first.
如果需要彻底清理整个缓存，您可以在一个指定缓存清理操作中调用函数Cache：clear，或者您也可以创建一个控制器来实现这一目的。
If you want to blow the whole cache clean, you can call the function cache: : clear either in a specific cache clearing action, or you could create a controller explicitly for that purpose.
现在只需使用一行代码，Catalog控制器就能够使用请求端缓存功能来缓存从遗留Catalog应用程序返回的Catalog了。
With one line of code, the catalog controller can now use the requester-side caching capabilities for caching the catalogs returned from the legacy catalog application.
高速缓存数据丢失，但控制器已恢复。
其原因可能是发生意外断电后，系统处于断电状态下的时间长度已超过电池续用时间，控制器已保护高速缓存。
This could be due to the fact that your controller had protected cache after an unexpected power loss and your system was without power longer than the battery backup time.
在群集中的主机控制器上使用回写高速缓存会影响性能。
Write-back caching cannot be used on host controllers in a cluster without hindering performance.
电池备份缓存有故障，更换备件号（FRU） 90P5245，控制器1，错误代码：31。
The battery-backup cache device, replacement part number (FRU) 90P5245, is defective: controller 1, Error code: 31
电池备份缓存设备需更换新电池，备件号（FRU） 90P5245，控制器1，错误代码：10。
The battery-backup cache device, FRU part number 90P5245, needs a new battery: controller 1, Error code: 10
利用多通道缓存串行口mcbsp实现SPI总线方式的数据采集，并采用两个DMA控制器实现了数据的实时传输和存储。
The use of multi-channel buffered serial port MCBSP is to achieve SPI bus (mode of) data collection, and the real-time data transmission and storage is achieved by the use of two DMA controllers.
如果您结合这要求域控制器身份验证以解锁工作站策略，了密码缓存在两个方向上都已关闭。
If you combine this with Require Domain Controller authentication to unlock workstation policy, you've got the password caches turned off in both directions.
如果您结合这要求域控制器身份验证以解锁工作站策略，了密码缓存在两个方向上都已关闭。
If you combine this with Require Domain Controller authentication to unlock workstation policy, you've got the password caches turned off in both directions.
应用推荐