Advanced XSLT programmers write XSLT in a functional programming style that emphasizes a stateless approach.
XSLT高级程序员以函数编程方式编写XSLT，这种方式强调无状态方法。
Declarative support for content negotiation works well and the default resource life-cycle encourages a stateless approach.
对内容协商的声明式支持也工作得很好，默认的资源生命周期鼓励无状态的方式。
Stateless failover is the simplest approach but also the least useful approach given that the approach maintains no state between the failed server and the backup server.
无状态的故障恢复是最简单的方法，但也是作用最有限的方法，因为该方法在故障服务器与备用服务器之间没有维护任何状态。
Therefore, we recommend that a stateless session bean approach be chosen for most applications.
因此，我们建议对大多数应用程序使用无状态会话Bean方法。
This approach is a little more limited, because it does not give you stateless performance — you are in fact using a separate thread per user.
这种方式有一点儿受限制，因为它不提供无状态性能——实际上是为每个用户使用一个单独的线程。
A stateless session performs even better than the previous approach, because it is a thin wrapper over JDBC and is able to bypass many of the operations required by the regular session.
无状态会话执行起来比上一种方法更好，因为它只是JDBC的简单包装，而且可以绕开很多常规会话要求的操作。
A stateless session performs even better than the previous approach, because it is a thin wrapper over JDBC and is able to bypass many of the operations required by the regular session.
无状态会话执行起来比上一种方法更好，因为它只是JDBC的简单包装，而且可以绕开很多常规会话要求的操作。
应用推荐