1·This article focuses on the command caching portion of this functionality.
本文集中讨论了这项功能的命令高速缓存部分。
2·In this example, caching was used to overly reduce the number of remote calls, but this approach also resulted in a performance degradation, not improvement.
在这个实例中，过度地使用高速缓存来减少远程调用的数量，但是该方法同样导致性能下降，而不是提高。
3·This architecture lets you decide at the time of deployment if you will use caching.
这个体系结构让您在部署时决定是否使用高速缓存。
4·When you need to reduce the number of calls further, you can employ caching techniques where applicable in the calling application.
当需要进一步减少调用的数量时，可以在调用应用程序中适当采用高速缓存技术。
5·Leave caching off unless you have a performance issue with the Home lookups and you don't have the limiting case described above.
关闭高速缓存，除非用户还有与主机查找相关的性能问题而且没有上面所描述的限制情况。
1·In this case, caching a service response and replaying the cached response the next time the service receives the same request is a valid and appropriate way to accelerate SOA service performance.
在这种情况下，缓冲服务响应并在服务再次收到同样的请求时重新使用缓冲的响应是一种提高SOA服务性能的合理而适当的方法。
2·So far, implementations have had to provide their own mechanisms for caching schemas.
到目前为止，实现必须提供自己的模式缓冲机制。
3·Previous versions of the allocator used a few search-ordering heuristics that made adequate guesses about caching, although with occasionally bad worst-case results.
以前版本的分配器使用一些搜索-排序尝试对高速缓冲进行足够的猜测，尽管偶然会遇到最坏情况。
4·First, SOA designs often overlook the potential for mid-tier service caching to accelerate SOA performance.
首先，SOA设计常常忽视了用中间层服务缓冲来提高SOA性能的可能性。
5·The effectiveness of caching obviously depends on the costs of splitting, coalescing, and searching relative to the work needed to track cached chunks.
很明显高速缓冲的有效性依赖于分割合并和查找的开销相对与用于跟踪被高速缓冲的块的开销。