Support the use of TGTs obtained from a credentials cache and secret keys obtained from key tables.
支持从凭证高速缓存获得的TGT的使用，支持从密钥表获得密钥的使用。
Instead, use an in memory hash table to cache the data and just keep a key to the data in the session.
相反地，应该使用内存中的哈希表来缓存数据，并且在会话中保存一个对此数据进行引用的键。
Where multiple credentials are available, for example, from a credentials cache or a key table, the choice of default credentials can be based on a number of factors.
在多个凭证可用的场合，例如，在一个凭证高速缓存或一个密钥表，对缺省的凭证的选择可取决于很多因素。
The login module can also use an existing TGT from a credentials cache or an existing secret key from a key table.
登录模块还可以使用一个来自凭证高速缓存的已存在的TGT或是来自密钥表的已存在的密钥。
The URL is the only key used to access a specific generated view in such a cache infrastructure.
URL是用于访问此类缓存基础结构中的特定生成视图的唯一的键。
It can be argued that the most recent addition to a key table or a credential cache is the most reasonable choice as a default; it is certainly one of the simplest choices.
这表明最经常添加到密钥表或凭证高速缓存的凭证是最合理的缺省选项；这当然是最简单的一种选择。
If the hash key is calculated from those parameters, previously generated versions of the same view can be retrieved easily from the cache.
如果用这些参数计算散列键，则很容易在缓存中找到同一视图的旧版本。
To do so, you would specify the action as an array key and the length of time to keep the views in cache, much like you did above.
为此，把这个操作指定为数组键并指定在缓存中保留视图的时间长度，像上面一样。
One key feature of both applications is that it allows users to cache music for offline play.
而这两款应用都有一个最为关键的功能，它可以让用户将音乐缓存到本地机器上，以供离线使用。
The cache request mediation generates a cache key based on the request message, and searches for a response in the cache.
缓存请求中介基于请求消息生成缓存键，并在缓存中搜索响应。
In order to make the generation of the cache keys reusable for individual projects, separate the key generation into its own class.
为了生成可供各个项目重用的缓存键，可以将键生成分类。
The example bookmark portlet shows how to use the different cache key scopes, and how to store the data with the WebSphere dynacache infrastructure.
示例书签Portlet展示了如何使用不同的缓存键范围，以及如何使用WebSpheredynacache基础设施存储数据。
When you define the sessionid to be part of the cache key, the portlet content is cached on a per user base.
当您将sessionid定义为缓存键的一部分时，Portlet内容是在每个用户的基础上进行缓存。
Performance in practice is paradoxically not degraded by this indirection and binding but rather enhanced as the URI address ACTS as a key to NetKernel internal cache.
实际的性能似乎不会因为这样的迂回和捆绑而降低，但是当把URI地址作为NetKernel内部缓存的主键时确实可以提高性能。
Performance can regress for simple portlets because cache key calculation becomes more expensive than recalculating the portlet response again.
对于简单Portlet，由于缓存键计算比重新计算Portlet响应开销更大，其性能可能会降低。
The servlet checks the cache using this key regularly until it can display the data.
Servlet使用该密钥定期检查缓存，直到它可以显示数据为止。
Before firing the back-end call, the run methods checks the Distributed Map cache with the unique key provided.
在执行后端调用前，run方法使用提供的唯一密钥检查分布式映射缓存。
Therefore, the cache key for portlets running in WebSphere Application Server is configurable in detail using cachespec.xml.
因此，可以使用cachespec . xml对在WebSphereApplicationServer中运行的Portlet的缓存键进行详细配置。
You need to supplement it with some additional cookies to make a composite cache key.
需要加上一些额外的cookie，形成复合的缓存键。
Caching multiple views for the same portlet is possible because the cache key contains the relevant information from the navigational state parameters.
由于缓存键包含来自于导航状态参数的相关信息，因此可以缓存同一个Portlet的多个视图。
Now that you know how to cache data using the dynacache infrastructure, let's look at how you can generate the correct cache key in a portlet.
既然您已经了解了如何使用dynacache基础设施缓存数据，现在让我们看一下如何在Portlet中生成正确的缓存键。
To cache a response from a web service, you need to generate a unique key to use for indexing it.
为了高速缓存一个来自Web服务的响应，您需要生成一个用来对它进行索引的唯一的密钥。
As with servlet caching, command caching requires a unique cache ID as the key for storing and retrieving something from the cache.
对于servlet高速缓存，命令高速缓存需要一个唯一的缓存id作为存储和从缓存中进行检索用的主键。
A key feature of WebSphere eXtreme Scale is that it provides a large, scalable, elastic cache.
WebSphereeXtremeScale的关键功能是提供大型、可扩展、弹性的缓存。
You invoke get with a key and if that key exists in the cache, the value will be returned.
您使用一个键来调用get，如果这个键存在于缓存中，则返回相应的值。
WebSphere Portal USES extra execution resources to calculate the internal cache key for the fragment cache.
WebSpherePortal将使用额外的执行资源计算机片断缓存的内部缓存键。
To support user-scoped caching, the Application Server administrator would need to specify that the cache key within the cachespec.xml use the sessionid.
为了支持按用户缓存，ApplicationServer管理员需要指定 cachespec.xml 中的缓存键使用sessionid。
The cache key for the fragments needs to be computed such that the complete navigational state of the portlet contributes to this key.
需要计算片段的缓存键，以确定是否向此键提供了Portlet的完整导航状态。
Now that you know how to create a session-based cache key, let's look into generating a cache that is unique for a portlet window in the next section.
既然已经了解了如何创建基于会话的缓存键，在下一部分中，我们看一下如何生成Portlet窗口的唯一缓存。
You invoke delete with a key and if that key exists in the cache, the value will be deleted.
您将使用一个键调用delete，如果该键存在于缓存中，则删除该值。
应用推荐