启用会话持久性。
If I don't need session persistence, can I turn it off?
如果我不需要会话持久性，是否将其关闭？
Speaking of session persistence, don't forget to enable it.
当谈及会话持久性时，不要忘记要启用这项功能。
You can use WebSphere eXtreme Scale or session persistence for session failover.
可以使用WebSphereeXtremeScale或会话持久性执行会话故障转移。
The manual update can be the most efficient means of session persistence if the attributes are infrequently updated.
如果属性更新不频繁，手动更新就可能成为最高效的会话持久性方法。
You can choose from database session persistence or memory-to-memory session replication for applications running in a cluster.
您可以为运行在集群中的应用程序选择数据库会话持久化或内存到内存的会话复制。
For example, a standard WebSphere Application Server environment pattern with in-memory session persistence and global security can be created.
例如，可以创建一个标准的WebSphereApplicationServer环境模式，其中包含内存会话持久性和全局安全性。
Further intelligence automatically constructs high availability messaging, global security, or session persistence as per the pattern definition.
智能进一步根据模式定义自动构建高可用性消息传递、全局安全性或会话持久性。
If instead, session persistence is enabled, WebSphere will automatically move the user (and their session) to another application server, transparently.
相反地，如果启用了会话持久性，WebSphere会自动将用户(以及他们的会话)移到另外一个应用服务器上去。
For example, applications should not put too much data into sessions to reduce the memory footprint of the server and to make session persistence easier and faster.
例如，应用程序不应将过多的数据放置到会话中，从而减少服务器的内存占用并更快速方便地保持会话。
Session persistence has been present in most major containers for many years (e.g. Restart persistence in Tomcat), but was notoriously absent in Glassfish before v3.
会话的持久化功能在大多数主流的容器中已存在多年(比如说Tomcat中的RestartPersistence)，但众所周知，在Glassfish的v3之前的版本中，这一功能是缺失的。
The set of advanced options include the ability to configure messaging, enable session persistence, and activate global security in the WebSphere Application Server environment.
高级选项包括配置消息、启用会话持久性和激活WebSphereApplicationServer环境中的全局安全性。
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.
数据库持久性的缺点在于数据库的成本，特别是存储在数据库中的会话数据本身应该具有高可用性的情况下更是如此。
Despite the drawbacks, J2EE architects have begun to claim plain vanilla stateless session beans with raw JDBC calls as the safest and most commonly recommended data persistence mechanism.
尽管还有不足，J2EE架构设计师已开始宣布带有原始jdbc调用的纯无状态会话bean是最安全和最受推崇的数据持久性机制。
It provided an implementation of remote session beans directly and used Castor for its implementation of container-managed persistence (CMP) entity beans.
它直接提供了一个远程会话bean的实现，并使用Castor作为它的容器管理持久性(CMP)实体bean的实现。
Because developers have complete control over the data access mechanism used within a session bean, data access and persistence logic can be optimized for certain tasks.
因为开发人员完全控制在会话bean中使用的数据访问机制，所以可以针对某些任务优化数据访问和持久性逻辑。
In a persistence architecture based on session beans and JDBC, a session bean delegates all access commands to the JDBC layer.
在基于会话bean和JDBC的持久性体系结构中，会话bean将所有访问命令都委托给jdbc层。
In this third installment of the J2EE pathfinder series, we have compared and contrasted entity beans with session beans and JDBC for data persistence.
在J2EE探险者系列的第三部分中，我们针对数据持久性将实体bean与会话bean和jdbc组合作了比较和对照。
My recommendation for a Network Deployment session distribution mechanism remains the same as stated in an earlier column, which is to employ database persistence.
我对NetworkDeployment会话分发机制的建议与在 前一个专栏中陈述的建议相同，即采用数据库持久性。
Session beans and JDBC make an excellent team for handling enterprise data persistence. The most commonly recognized advantages to this combination are as follows.
会话bean和JDBC成为处理企业数据持久性的极佳组合。
A local EJB session facade is created to wrap Hibernate persistence.
创建本地e jb会话facade以包装Hibernate持久性。
Those services are DynaCache, memory to memory session replication, core groups, Web services caching, and stateful session bean persistence.
这些服务是DynaCache、内存到内存会话复制、核心组、Web服务缓存和有状态会话Bean持久性。
Those services are DynaCache, memory-to-memory session replication, core groups, Web services caching, and stateful session bean persistence.
这些服务是DynaCache、内存到内存会话复制、核心组、Web 服务缓存和有状态会话bean持久化。
The session interface manages persistence during the lifecycle of a Hibernate session.
在Hibernate会话的生命周期中，Session接口管理持久性。
A downside of the Open Session in View pattern is that the persistence-context object is effectively scoped to a user request.
OpenSessioninView模式的一个缺点是持久化上下文对象被高效地划定到用户请求作用域内。
In the following screen capture, you can see persistence session information for source IP 10.102.3.108.
在下面的截图中，你可以看到关于源地址10.102.3.108这个IP的持续性session信息。
When open Session in view is implemented as a filter or interceptor, the persistence-context object remains open during view rendering.
当openSessioninView模式作为过滤器或拦截器实现时，持久化上下文对象在视图呈现期间会保持打开状态。
There are other possible solutions like cookie session store (session size is limited, no sensible data in sessions), memcached (too much RAM when you have many sessions + no persistence).
还有其他的解决方案如cookie会话仓库(会话长度有限，不能在会话中存放敏感数据)，memcached(无法持久化+难以实现高可用性方案)。
The session focuses on the troubleshooting aspects of the designs, including server connectivity, persistence, and scripted health checking.
本课程重点介绍排除设计方面的故障，包括服务器连接、持续连接和脚本状态检查。
The session focuses on the troubleshooting aspects of the designs, including server connectivity, persistence, and scripted health checking.
本课程重点介绍排除设计方面的故障，包括服务器连接、持续连接和脚本状态检查。
应用推荐