缓存

网页浏览器的高速缓存区里有你最近下载的网页文件。

In your Web browser 's cache are the most recent Web files that you have downloaded .

基于Web日志和缓存数据挖掘的个性化推荐系统

Personalization Recommendation System Based on Web Log & Cache Data Mining

让web浏览器正确缓存内容很重要。

It is important to ensure that the web browser caches your content correctly .

监控Web服务结果缓存

Monitoring the web services result cache

Web代理缓存技术是改善网络性能，缓解网络瓶颈最有效的方法。

Proxy Cache is the most important technique to solve the Web traffic and relax net bottleneck .

分散型Web缓存模型

Decentralized Web Caching Model

WEB缓存的一致性是WEB缓存研究的难点之一，其决定缓存的可用性和正确性。

WEB cache consistency is one of the most difficult question in the research area of web cache .

如果这个数字在连续执行SHOWSTATUS命令时快速增加，就应该尝试增大线程缓存。

If this number increases quickly between successive SHOW STATUS commands , you should look at increasing your thread cache .

eXtremeScale缓存服务主要有两部分：目录服务器和容器服务器。

The eXtreme Scale caching service has two parts : catalog servers and container servers .

DocumentManager缓存和服务配置

Document Manager cache and services configuration

请求端缓存模式（RequestorSideCachingPattern）规范可改进服务性能。

The Requestor Side Caching Pattern specification improves the service performance .

下一步是缓存在响应请求时创建的完整XML文档。

The next step would be to cache the complete XML documents that are created upon requests .

如果该请求可缓存，则XML代理将执行标准端缓存操作。

If the request is cacheable , the XML proxy will perform a standard side cache operation .

有一个Web页面会显示这些数据，例如表缓存的使用情况、关键字效率、连接上的客户机以及临时表的使用情况。

A Web page displays the data , such as table-cache usage , key efficiency , connected clients , and temporary-table usage .

在部署了WAS集群模式之后，企业可以随时使用eXtremeScale缓存服务。

After the WAS cluster pattern is deployed , the eXtreme Scale caching service is ready for business .

协作缓存CC（CooperativeCache）技术将各服务器的内存协调工作，形成全局的cache。

Cooperative cache makes each memory work together and forms a global cache .

如果使用缓存exchange模式，则应考虑用户下载脱机地址列表时对服务器的影响。

If you use cached exchange mode , you should consider the effect on the server when users download offline address lists .

过去，Web服务器会缓存响应数据，仅在接受到足够的字节数或块数后才会发送出去。

Traditionally , Web servers cache the response data and only send it after a sufficient number of bytes or chunk has been received .

WebSpherePortal为远程缓存所使用的唯一失效机制是过期超时。

The only invalidation mechanism that WebSphere Portal uses for remote caches is expiration timeout .

在最高层是cachechain，这是一个slab缓存的链接列表。

At the highest level is the cache_chain , which is a linked list of the slab caches .

每当一个用户通过Web应用接口作了某些更改时，XML缓存或响应缓存必须执行相关性检查。

Every time a user makes some changes through the Web application interface , XML or response caches must be checked for dependencies .

WebSphereeXtremeScale的关键功能是提供大型、可扩展、弹性的缓存。

A key feature of WebSphere eXtreme Scale is that it provides a large , scalable , elastic cache .

服务器将此用户安全信息缓存到称为Java™Subject的内存内对象，以避免出现进一步的身份验证提示。

The server caches this user security information in an in-memory object known as a Java ™ Subject to avoid further authentication challenges .

WebSpherePortal将使用额外的执行资源计算机片断缓存的内部缓存键。

WebSphere Portal uses extra execution resources to calculate the internal cache key for the fragment cache .

manifest参数的值是到该Web页面的缓存清单文件的URL。

The value of the manifest parameter is the URL to the Web page 's cache manifest file .

访问缓存中的这些项的唯一方法就是请求URL。

The only way to address such entries in the cache is the request URL .

在前面的“在流程服务器中启用动态缓存服务”部分中，您在安装ProcessServer时附带安装了DynamicCacheMonitor应用程序。

In previous section Enable dynamic cache service in process server you have installed the Dynamic Cache Monitor application shipped together with the Process Server installation .

围绕内容分发网络内容路由技术，给出了两种基于网络拓扑的算法&“简单算法”和“拓扑分割算法”，确保用户的Web请求被指向距离其最近的和最可用的高速缓存服务器。

The paper presents two algorithms about CDN content routing algorithm : " the Simple Algorithm " and " the Segment Algorithm ", which can achieve network proximity .

如果对这个Web服务的调用不多（每分钟少于一个），那么可以确定没有必要进行高速缓存。

If the calls to this web service are infrequent ( less than one a minute ), it might be determined that there is no need for caching .

如果服务器出现故障，客户机API软件将把缓存读写操作重新路由到正常运行的备用服务器上。

If servers fail , the client API software reroutes your cache reads and writes to a working alternate .