在数据库中存储会话状态的成本可能难以承受。
Storing conversational state in the database can be prohibitively expensive.
取决于该的应用程序体系结构的更改可能包括令人生畏任务如同步会话状态和跨服务器位置复制数据库事务。
Depending on the application, changing the architecture could include daunting tasks such as synchronizing session state and replicating database transactions across server locations.
有时候这仅仅是某种类型的会话id，它可以用来从内存或数据库检索服务器端状态。
Sometimes this may just be a session id of some sort that can be used to retrieve server-side state from memory or a database.
此外，无状态很难实现，可能会导致多次往返数据库来获取本来通常存储在会话上下文中的信息。
Additionally, statelessness can be difficult to achieve and can lead to multiple round trips to the database for information that is normally stored within the context of the session.
无状态会话Bean使用 DBHelper 类（使用了JDBC声明）执行数据库事务。
The stateless session bean uses the DBHelper class (JDBC statements are used) to perform the database transaction.
为了清空数据库，程序使用一个无状态会话bean自动启动CMT。
To clear the database, the program USES a stateless session bean that automatically starts CMTs.
在大多数CGI应用程序中，大部分状态存储在数据库中，只有会话id通过cookie传递给每个脚本。
In most CGI applications, much of the state is stored in a database, but only a session ID is passed to each script via a cookie.
在J2EE应用程序中存储服务器端状态的其他方法是使用有状态会话bean，或者在数据库中存储会话状态。
The other alternatives for storing server-side state in J2EE applications is to use stateful session beans, or store conversational state in the database.
具有容器管理事务方法的无状态会话bean，如清单5和清单6所描述的，降低了管理数据库实体的复杂性。
The stateless session bean with container-managed transactional methods, as described in Listing 5 and Listing 6, reduce the complexity involved with managing database entities.
NET只在真正需要时才访问会话状态数据库。
NET only accesses the session state database when it really needs to.
这样做总是一个好办法，但是当会话状态存储在数据库中时，该方法尤其重要。
It's always a good idea to do so, but it's especially important when session state is stored in a database.
这样做总是一个好办法，但是当会话状态存储在数据库中时，该方法尤其重要。
It's always a good idea to do so, but it's especially important when session state is stored in a database.
应用推荐