在模拟器内配置的设备的会话数据的运行时视图。
Runtime views of the session data for devices configured within the simulator.
第二部分叙述了管理用户和会话数据的一些方法。
The second part described methods for managing users and session data.
会话数据所适合的示例场景是Internet站点的购物车。
An example scenario when session data is appropriate is the shopping cart on an Internet site.
除了决定如何存储复制会话数据，还有什么时候复制数据的问题。
In addition to deciding how to store replicated session data, there is also a question of when to replicate data.
由于需要保留会话数据，因此系统内存不足时，无法丢弃任何数据。
Session data needs to be kept, so the system cannot discard any data when running low on memory.
当事件发生在更改会话数据的模拟器时，视图将动态地更新到反映当前的状态。
When events occur in the simulator that change the session data, the views are dynamically updated to reflect the current state.
会话数据是临时的，通常短期存在，需要在页面的呈现过程中被迅速地访问到。
Session data is transient, usually short lived, and needs to be accessed quickly during the rendering of pages.
如果你不想丢失使用AR会话插件创建的旧会话数据，你可以设置。
If you do not like to loose old sessions created with default AR sessions plugin, you could set.
解决这个问题要求会话亲缘关系，它使得会话数据只持久化到一个资源库中去。
Solving this problem requires session affinity, which persists the session data to a repository.
它采用了一种无共享方法(尽管它会自动地将会话数据存储到一个通用数据库)。
It takes a Shared nothing approach (though it does automatically store session data to a common database).
在失败发生时，对会话数据的访问将更快，因为它位于内存中，数据本身也高度可用。
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 fact, once you think about that, the details of how session data is stored on the server are surprisingly trivial for purposes of understanding session handling.
视图将导致XSL模板将会话数据的XML表示转换为返回到客户机浏览器的本地化的HTML。
The view causes an XSL template to transform the XML representation of the session data into localized HTML returned to the client browser.
如果原始集群节点出现问题(故障转移情况)，则会话数据还必须复制到其他的集群节点。
The session data also needs to be replicated to other cluster nodes, in case the original cluster node goes down (failover scenario).
然后，Portlet可以使用此首选项属性来对每个Portlet定义的会话数据设置名称空间。
The portlet can then use this preference attribute to namespace the session data per portlet definition.
这也意味着你不需要关心SpringWebFlow会话数据的大小是否超过了物理堆大小。
What this means is that you do not need to care about if the size of the conversational data that Spring Web Flow has exceeds the physical heap size.
当会话数据写入到远程副本时，对会话数据进行序列化和反序列化所需的时间可能变得非常大。
The time it takes to serialize and deserialize session data when they are being written to a remote copy can become considerably large.
SessionManager可以加密保存在会话文件和已关闭的窗口文件中的会话数据。
Session Manager can encrypt session data stored in session files as well as the closed window file. To enable this feature, do the following.
相似地，如果您正在通过群集几个计算机来实现负载平衡，那么会话数据只存储在创建它的计算机上。
Similarly, if you are doing load balancing by clustering several computers, the session data is stored only on the computer that created it.
您实际上只需知道数据被可靠地存储，只需提供一个键(常常称为会话键或会话id)，就可以访问会话数据。
All you really need to know is that data is reliably stored and can be accessed given only a single key, usually called the session key or session ID.
然后它创建一个VisitInformation对象的实例，(标记为“visits”)，它拥有会话数据。
Then it creates an instance of the VisitInformation object (labeled "visits") that holds the session data.
这种方法相当直观，其优点是不仅会话可以故障转移到其他主机，而且即使整个群集失效，会话数据也可以保存下来。
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.
相反，seam小心地管理那个区段的会话数据的生命周期，并且当conversation终止时，自动清除它们。
Instead, the life cycle of that segment of session data is carefully managed by Seam and it is automatically cleaned up when the conversation terminates.
但是，如果会话数据与某个新索引冲突(比如重复行在唯一的索引上冲突)，则在数据纠正之前不会为该会话物化该索引。
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.
数据库持久性的缺点在于数据库的成本，特别是存储在数据库中的会话数据本身应该具有高可用性的情况下更是如此。
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.
同样，即使存根可能与运行在相同后端服务器的服务进行对话，典型的JAX - RPC运行时也分别为每个单独的存根维护会话数据。
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.
Reddit的所有内容都使用了memcache：数据库的数据、会话数据、渲染的页面、存储的内部函数、预先计算的页面、全局锁。
Reddit started to use memcache for about everything: database data, session data, rendered pages, memorizing internal functions, pre-computed pages, global locking.
它可以给予您无限地存储会话数据的能力，使您的会话数据不仅可以在重新启动后检索，还可以从群集中许多机器中的任意一个检索。
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.
Body元素包含Web服务将要处理的信息，而Header 元素包含特定于应用程序的信息，比如身份验证数据和会话数据等。
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.
会话数据具有用户会话的生存期，是基于用户执行的操作（将转换为Portlet 中的 processAction调用）创建的。
Session data is that which has a lifetime of the user session, and is created based on actions the user performed that translate to processAction calls on the portlet.
应用推荐