Whereas the cache API is designed to cache data for a long period or until some condition is met, per-request caching simply means caching the data for the duration of the request.
缓存api的设计目的是为了将数据缓存较长的一段时间，或者缓存至满足某些条件时，但每请求缓存则意味着只将数据缓存为该请求的持续时间。
It will use a set of caching policy rules to determine the cacheability of each incoming request.
它将使用一系列缓存策略规则以便确定每一个传入请求的可缓存性。
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服务性能的合理而适当的方法。
This field is used to specify directives that must be obeyed by all caching mechanisms along the request/response chain.
这个字段用于指定所有缓存机制在整个请求/响应链中必须服从的指令。
A caching proxy that receives a request searches for matching responses that might already exist in its cache.
接收请求的缓存代理将在其缓存中搜索可能已经存在的匹配响应。
Data caches can be used for caching data with change rates that are below the page request rate.
可以使用数据缓存对那些更改频率低于页面请求频率的数据进行缓存。
Caching means to store the results of an expensive request for later use.
缓存意味着把处理成本很高的请求的结果存储起来，供以后使用。
The rules are application specific, but in general, caching policy rules can trigger on the request URI, specific XML contents within the request body, or a combination of both.
这些规则是特定于应用程序的，但一般情况下，可在请求URI 中、请求正文中的特定XML内容或两者的组合中触发缓存策略规则。
You can also define caching rules for caching dynamic content based on request parameters or other application metadata.
还可以根据请求参数或其他应用程序元数据定义缓存动态内容的缓存规则。
In this caching scenario, when the cache mediation finds a response to a service request in the cache, it will return the cached response directly to the message requester.
在此缓存方案中，当缓存中介在缓存中发现服务请求的响应时，会将所缓存的响应直接返回给消息请求者。
Therefore, if the result of an application request is retrieved from the elastic caching tier, the application processing and processing latency for that request are eliminated.
因此，如果从弹性缓存层检索到应用程序请求的结果，则会清除应用程序处理和此请求的处理延时。
A caching device needs to parse all of the request and response headers in order to find answers to those questions.
缓存设备需要解析所有请求和响应报头，以便找到这些问题的答案。
Most applications that request this data, however, employ some form of caching, as network round-trips are very expensive.
然而，大多数请求这个数据的应用程序使用了一定程度的缓存，因为网络往返开销很昂贵。
Only a good approach of caching the results and not re-running the transformations upon every request can save the performance here.
只有很好地缓存了结果而不需每次请求都重新运行转换，才能保证性能。
Various parts of the SOAP message can be used to uniquely identify the request for caching.
SOAP消息的不同部分能够被用来惟一地验证对于高速缓存的请求。
Cache identification has been introduced with additional request parameters to facilitate application version caching.
引入了具有附加请求参数的缓存标识，以便简化应用程序版本缓存。
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.
此外，要使资源请求可缓存，您需要在响应上显式设置缓存控制信息，以便门户能够生成缓存标头。
There are, of course, other options that may be even better here, such as caching the results of the query on the server and rebinding the control with each request.
当然，有一些其他可能更好的选择，例如缓存服务器的查询结果，每次发出请求时重新绑定控件。
Generally, caching happens anytime a request is made, and the responding application says, "I don't have to go get that."
通常，如果发出请求，且应用程序响应“我没必要再去获取数据。”
With portlet caching, the portal aggregates cached portlet fragments into complete pages before responding to a request.
利用Portlet缓存，门户会在响应请求前将缓存的Portlet片段聚合为完整的页。
The proxy cache in front of your Web application reassembles the final document based on the parts, and is responsible for caching some components and making the request for others.
Web应用程序前面的代理缓存根据各个部分重新组装最终的文档，负责缓存一些组件并为其他组件发出请求。
The following picture illustrates the basic principles for SOAP request to call caching web services using dynamic cache.
以下图片展示了SOAP请求使用动态缓存调用缓存Web服务的基本原理。
Since for a Web application most of the pages will be generated only on request, caching will not happen and hence compression is suited for these types of applications.
对于Web应用程序，大多数页面都只在请求时才生成，所以缓存不会发生，因此压缩非常适合这类应用程序。
When caching is involved, an HttpModule in ASP.NET receives the request, and returns the contents from the Cache.
涉及到缓存时，ASP.NET中的HttpModule会接收该请求，并返回缓存中的内容。
Performance: the cache increases the responsiveness of the service by caching request and corresponding response messages.
性能：缓存将缓存请求和对应的响应消息，从而提高服务的响应能力。
Requests use POST and require a complex XML request to be created, which makes response-caching difficult.
请求使用POST且需要创建一个复杂的XML请求，这使得响应缓存难以实现。
Figure 2 describes the caching capabilities of WebSphere Portal on different levels as a request flows from the user's browser to the backend system.
图2描述了在请求从用户的浏览器传到后端系统期间，WebSpherePortal不同级别上的缓存功能。
不缓存也不请求重试。
Without caching, your application must request the data from the database each time a user wants to view a product.
在不使用快取的情况下，每次使用者想要检视产品时，您的应用程序都必须要求资料库提供资料。
Without caching, your application must request the data from the database each time a user wants to view a product.
在不使用快取的情况下，每次使用者想要检视产品时，您的应用程序都必须要求资料库提供资料。
应用推荐