Just as predicted, overloaded resource names and a caching service locator makes the code execute differently; it makes some components get the wrong resources.
正如所预测的那样，重载的资源名和缓存服务定位器使得代码执行有不同的结果，它使某些组件取得错误的资源。
Sure, the component got the wrong resource and therefore didn't work right, but thanks to caching, it failed really fast.
当然，组建取得了错误的资源当然不能正常工作，但是，要感谢缓存，它失败的却是很快。
The server resource issue can be addressed by caching prior data and then aggregating the very newest additions.
服务器资源问题可以这样解决：将以前的数据缓存，然后将最新添加的数据集成进来。
When two components use a resource name that is overloaded — that is, a name that is bound to two different resources — a caching service locator returns the same resource to both components.
当两个组件使用一个重载的资源名，也就是说，一个名称绑定到两个不同的资源，缓存服务定位器为两个组件返回相同的资源。
Even if caching does improve performance, that's little comfort when a component fails to receive the resource it is mapped to.
即使缓存能提高性能，当组件接收它所映射的资源失败时，也是一件痛苦的事情。
When resource lookups are expensive, caching improves performance by avoiding the repeated lookup of the same resource.
当资源查找代价很高时，缓存通过避免重复查找相同资源而提高了效率。
Also, to make a resource request cacheable, you need to explicitly set the cache control information on the response so that the portal can generate caching headers.
此外，要使资源请求可缓存，您需要在响应上显式设置缓存控制信息，以便门户能够生成缓存标头。
OK, so a caching service locator causes errors for overloaded resource names.
好，既然是由于缓存服务定位器导致重载资源名时的错误。
Write-through caching pattern is used by the applications to write data to the cache which causes writes to an underlying resource (e.g. a database).
直写式缓存模式被用于将数据写入底层资源(如数据库)的缓存。
In the case of HTTP caching, the cache entries are invalidated in case an interaction with the resource occurs that potentially modifies the server side state of the resource.
对于HTTP缓存，在出现可能修改资源的服务器端状态的资源交互时，缓存项将失效。
Typically the use of the URL for a resource alone may not be sufficient as the caching key.
通常，只使用资源的URL作为缓存键可能不够。
This includes using Bigtable and Memcache together to provide caching of "expensive" data - data that takes a long time to retrieve from a remote resource.
这包括同时使用Bigtable和Memcache来提供“昂贵”数据的缓存—需要花费很长时间才能从远程资源中检索到的数据。
Browser and gateway proxy caching of resource representations.
资源表示形式的浏览器与网关代理缓存。
When the Service Locator pattern was first developed for J2EE 1.2, caching resource references was a good idea because JNDI lookups were often slow and hurt performance.
当首次使用ServiceLocator模式开发J2EE 1.2应用程序时，因为JNDI查找时常降低甚至有损于执行性能，所以缓存资源引用在当时是一个很好的主意。
Client resource index caching mechanism and the iterative query forward mechanism are adopted in the system design to enhance the search efficiency and success ratio.
系统采用客户资源索引缓存机制和“迭代深入”的查询转发机制，提高了搜索的效率和成功率。
Client resource index caching mechanism and the iterative query forward mechanism are adopted in the system design to enhance the search efficiency and success ratio.
系统采用客户资源索引缓存机制和“迭代深入”的查询转发机制，提高了搜索的效率和成功率。
应用推荐