This represents flush-cached data.
这表示要刷新缓存数据。
The region USES a remote server that handles the cached data.
这个区域使用一台远程服务器处理缓存数据。
It is recommended to use a separate partition for storing the cached data.
建议使用单独的分区来存储缓存的数据。
With JCS, you can store cached data in different data regions that you specify.
使用JCS可以在各种指定的数据区域中存储缓存数据。
Now that you've seen the API, it's time to define where the cached data will go.
看过了API之后，现在就可以定义缓存后的数据的去处了。
The application is still required to parse the cached data before it displays it.
该应用程序仍需要每次在显示缓存数据前解析。
Each server added increased cache redundancy and difficulty in accessing cached data.
每台服务器在访问缓存数据时的复杂性都增加了，而且还加入了更多的缓存冗余。
For demonstration purposes, I've thrown a RemoteException to show the use of cached data.
出于演示目的，我引发了一个RemoteException异常来表明使用的是缓存数据。
Since each run repeats the same list of requests, each subsequent run should serve cached data.
由于每次运行重复同样的要求清单，以后每次运行要为缓存的数据。
This is all typical code for managing both locally cached data, and live data from the servers.
这是用于同时管理本地缓存的数据和来自服务器的实时数据的典型代码。
When the memory cache region becomes full, LRU removes the least recently used cached data first.
当内存缓存区域满时，lru会首先删除最近最少使用的缓存数据。
The remote cached server can be used by multiple JCS client applications to store the cached data.
这台远程缓存服务器可以被多个JCS客户端应用程序用于存储缓存数据。
This example is somewhat contrived in that it simply displays the cached data as-is, using a portlet.
这个实例多少有点刻意，因为它使用portlet只显示现有的缓存数据。
Note: The above issue resolution is not solvable if we are eagerly fetching the second level cached data in our query.
说明：如果在查询中使用预先抓取来获取二级缓存中的数据时，我们将无法解决上面提出的问题。
Dynamic cache can take advantages of DRS in the application server to replicate cached data across servers in a cluster.
动态缓存可以利用应用服务器中的DRS在集群的各个服务器中复制缓存的数据。
To improve performance, JCS stores the cached data keys in memory while storing the actual cached data on the file disk.
为了提高性能，JCS在文件磁盘上存储实际缓存数据的同时，会在内存中存储缓存数据键。
In addition, to a corrupted journal, you also run the risk of losing drive cached data in the advent of a power failure.
而且，除了不一致的事务日志，当电源崩溃时你有可能面临磁盘缓存数据的丢失。
As a result, they don't provide an alternative to running an application server with a 64-bit JVM to hold the cached data.
因此，它们并不提供使用 64位JVM保存缓存数据运行应用服务器的替代方案。
Client pages are pages containing cached data for all other file systems (for example, JFS2 and Network file system (NFS)).
客户端分页是一些包含所有其他文件系统(例如，JFS2和网络文件系统(NFS))的缓存数据的分页。
If cached data is available, it is immediately loaded into the application so that the application becomes usable very quickly.
如果所缓存的数据可用，它就会立即被载入到应用程序内以便应用程序能立即可用。
By configuring correctly, DRS replicates the cached object across the whole cluster and keeps the consistency of the cached data.
通过合适的配置，DRS可以在整个集群范围内复制缓存的对象并保持缓存数据的一致性。
If new data is not available or accessible, you can continue to use cached data until new data becomes available and is fully downloaded.
如果新的数据不可用或不可访问，可以继续使用所缓存的数据，直至新数据可用且可完全下载。
There is no need to forcibly reload the cached data, you can use the standard access to load and populate the cache with information.
没有必要强制重载已缓存了的数据，可以使用标准的访问来用信息加载和填充缓存。
If the parts of the grid were cycled for routine maintenance, then this would result in some cached data being lost if there was no replication.
如果出于日常维护对网格的一部分加以循环利用，在没有副本的情况下就会致使一些缓存数据丢失。
This works fine on a single computer, but when you move to a clustered model, it's important that cached data remain consistent across all nodes.
在单一计算机上，这种方式工作得很好，但是在进入集群模型时，重要的是缓存的数据要在所有节点间保持一致。
In this case, the portlet renders the markup fragment based on the cached data, and the portal aggregates the markup into a complete portal page.
这种情况下，Portlet根据缓存的数据呈现标记片段，而门户将标记聚合为完整的门户页。
And you can't simply disconnect them either, as there's a possibility you'll lose locally cached data that hasn't yet been written to the device.
你不能只简单地将其拔下，因为这样你可能会丢失本地缓存中尚未写入该设备的数据。
For example, you could use the maximum life and expiration time for each cached item to refresh cached data for specific users that need updated data.
例如，您可以使用每个缓存项的最长生命周期和过期时间来为需要更新数据的特定用户刷新缓存数据。
The greater the number of server instances, the greater amount of invalidation chatter is required to keep the cached data fresh among the server instances.
服务器实例数量越多，要保持服务器实例间的缓存数据新鲜需要的无效交谈也就越多。
Therefore, it is useful to get the data only once, cache it, and have all other components use the cached data, instead of accessing the backend system again.
因此，只一次获取数据，对数据进行缓存，并让所有其他组件使用该缓存的数据，而非再次访问后端系统，这是很有益的。
应用推荐