处理会话数据。
Where is the session data stored.
会话的数据储存在什么地方呢？
Session data is stored on the server.
会话数据存储在服务器上。
User registration, profile, session data.
用户注册、个人资料、会话数据。
Both are used to support per-session data.
两者都用于支持基于会话的数据。
Session data must be replicated quickly as a form of backup.
会话数据必须以备份的形式迅速进行复制。
Session data has different characteristics from business data.
会话数据与业务数据有不同的特征。
Wait a minute… where are we going to store the user session data?
等等...我们要把用户会话数据存放在哪儿？
Thus, it addresses session data maintenance in a Web application.
因此，它实现了在Web应用程序中保持会话数据。
Session data can be used to greatly simplify accessing information.
会话数据可用于大大简化信息的访问。
What happens to the client session data in case the original server crashes?
如果原始服务器坏掉，对这个客户会话数据将会有什么样影响？
But I will give you a hint: Think more carefully about the user session data.
但我会给你们个提示：仔细思考一下用户会话数据。
Runtime views of the session data for devices configured within the simulator.
在模拟器内配置的设备的会话数据的运行时视图。
The alternative is to store your session data in a different place, like a database.
备选方法是把会话数据存储在其他位置中，比方说数据库。
They normally maintain large session data at the client side, which improves performance.
它们通常在客户端维护大量会话数据，这有助于提高性能。
The commit statement restores the session data to the previous commit or rollback statement.
提交语句会将会话数据恢复为之前的提交或回滚语句。
An example scenario when session data is appropriate is the shopping cart on an Internet site.
会话数据所适合的示例场景是Internet站点的购物车。
Session data needs to be kept, so the system cannot discard any data when running low on memory.
由于需要保留会话数据，因此系统内存不足时，无法丢弃任何数据。
Solving this problem requires session affinity, which persists the session data to a repository.
解决这个问题要求会话亲缘关系，它使得会话数据只持久化到一个资源库中去。
The portlet can then use this preference attribute to namespace the session data per portlet definition.
然后，Portlet可以使用此首选项属性来对每个Portlet定义的会话数据设置名称空间。
Then it creates an instance of the VisitInformation object (labeled "visits") that holds the session data.
然后它创建一个VisitInformation对象的实例，(标记为“visits”)，它拥有会话数据。
It takes a Shared nothing approach (though it does automatically store session data to a common database).
它采用了一种无共享方法(尽管它会自动地将会话数据存储到一个通用数据库)。
Session data is transient, usually short lived, and needs to be accessed quickly during the rendering of pages.
会话数据是临时的，通常短期存在，需要在页面的呈现过程中被迅速地访问到。
In addition to deciding how to store replicated session data, there is also a question of when to replicate data.
除了决定如何存储复制会话数据，还有什么时候复制数据的问题。
When events occur in the simulator that change the session data, the views are dynamically updated to reflect the current state.
当事件发生在更改会话数据的模拟器时，视图将动态地更新到反映当前的状态。
The session data also needs to be replicated to other cluster nodes, in case the original cluster node goes down (failover scenario).
如果原始集群节点出现问题(故障转移情况)，则会话数据还必须复制到其他的集群节点。
The time it takes to serialize and deserialize session data when they are being written to a remote copy can become considerably large.
当会话数据写入到远程副本时，对会话数据进行序列化和反序列化所需的时间可能变得非常大。
In the event of a failure, access to the session data will be faster, since it is in memory, and the data itself remains highly available.
在失败发生时，对会话数据的访问将更快，因为它位于内存中，数据本身也高度可用。
In the event of a failure, access to the session data will be faster, since it is in memory, and the data itself remains highly available.
在失败发生时，对会话数据的访问将更快，因为它位于内存中，数据本身也高度可用。
应用推荐