处理会话数据。
Where is the session data stored.
会话的数据储存在什么地方呢？
User registration, profile, session data.
用户注册、个人资料、会话数据。
Both are used to support per-session 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应用程序中保持会话数据。
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.
它们通常在客户端维护大量会话数据，这有助于提高性能。
An example scenario when session data is appropriate is the shopping cart on an Internet site.
会话数据所适合的示例场景是Internet站点的购物车。
The portlet can then use this preference attribute to namespace the session data per portlet definition.
然后，Portlet可以使用此首选项属性来对每个Portlet定义的会话数据设置名称空间。
It takes a Shared nothing approach (though it does automatically store session data to a common database).
它采用了一种无共享方法(尽管它会自动地将会话数据存储到一个通用数据库)。
In addition to deciding how to store replicated session data, there is also a question of when to replicate data.
除了决定如何存储复制会话数据，还有什么时候复制数据的问题。
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.
在失败发生时，对会话数据的访问将更快，因为它位于内存中，数据本身也高度可用。
Similarly, if you are doing load balancing by clustering several computers, the session data is stored only on the computer that created it.
相似地，如果您正在通过群集几个计算机来实现负载平衡，那么会话数据只存储在创建它的计算机上。
Session Manager can encrypt session data stored in session files as well as the closed window file. To enable this feature, do the following.
SessionManager可以加密保存在会话文件和已关闭的窗口文件中的会话数据。
The disadvantage of database persistence is the cost of the database, particularly if the session data stored in the database should itself be highly available.
数据库持久性的缺点在于数据库的成本，特别是存储在数据库中的会话数据本身应该具有高可用性的情况下更是如此。
It can give you the ability to store indefinitely your session data where it can be retrieved not only after a restart, but from any of a number of machines in a cluster.
它可以给予您无限地存储会话数据的能力，使您的会话数据不仅可以在重新启动后检索，还可以从群集中许多机器中的任意一个检索。
As such, a typical JAX-RPC runtime maintains the session data separately for each individual stub even though stubs may talk with services running at the same back-end server.
同样，即使存根可能与运行在相同后端服务器的服务进行对话，典型的JAX - RPC运行时也分别为每个单独的存根维护会话数据。
The Body element contains information intended for the web service to process and the Header Element contains application specific information like authetication data,session data etc.
Body元素包含Web服务将要处理的信息，而Header 元素包含特定于应用程序的信息，比如身份验证数据和会话数据等。
The WS-Addressing session model provides coupling between the Web service endpoint information and the session data, which is analogous to object references in distributed object systems.
WS - Addressing会话模型提供了Webservices端点信息和会话数据间的耦合，这与分布式对象系统中的对象引用类似。
This approach is straightforward enough, and has the advantage that not only can the session fail over to any other host, but the session data can survive the failure of the entire cluster.
这种方法相当直观，其优点是不仅会话可以故障转移到其他主机，而且即使整个群集失效，会话数据也可以保存下来。
However, if the session data conflicts with a new index, (such as duplicate rows conflicting with a unique index), the index is not materialized for that session until the data is corrected.
但是，如果会话数据与某个新索引冲突(比如重复行在唯一的索引上冲突)，则在数据纠正之前不会为该会话物化该索引。
However, if the session data conflicts with a new index, (such as duplicate rows conflicting with a unique index), the index is not materialized for that session until the data is corrected.
但是，如果会话数据与某个新索引冲突(比如重复行在唯一的索引上冲突)，则在数据纠正之前不会为该会话物化该索引。
应用推荐