The second design directly violates the client-stateless-server constraint.
第二种设计直接违背了客户机-无状态-服务器约束。
Soon you begin to question whether violating the client-stateless-server constraint was such a good idea after all.
很快您就会质疑，违背客户机-无状态-服务器约束是否真的是一个好主意。
If state is always provided by the client, the server remains (at least from a programmer's viewpoint) stateless: There is no data to maintain, just incoming data to process as it shows up.
如果状态总是由客户机提供，服务器就是无状态的(至少从程序员的角度来看)：不会维护数据，只需处理传入的数据。
The first is to send a massive amount of state information with each client request, so that each request is context-complete and the server can remain stateless.
第一种设计要在每个客户机请求中都发送大量状态信息，因此每个请求都完整地保留了上下文的内容，服务器是无状态的。
A stateless server is more realistic in practice when the client is only requesting resources.
在客户端仅仅请求资源时，采用无状态服务器实际上是更现实的。
If there are multiple stateless app servers, you can just cut a client loose when it has passed a "reasonable" amount of time, and let it try its luck with a different app server.
如果有多个无状态的应用服务器，而一个请求已经花费了“一定”的时间，那就快刀斩乱麻，让它在其他应用服务器上试试运气吧。
This unification scheme solves the critical problem of how a stateless server can support client transactions without holding any client context and without sacrificing an ACID transaction warranty.
这个统一模式解决了一个无状态服务器如何在既不保存任何客户环境又不牺牲ACID 事务完整性的前提下支持客户端事务的重要问题。
The Web brought some unique challenges to software developers, most notably the stateless connection between the client and the server.
Web向软件开发人员提出了一些特有的挑战，最明显的就是客户机和服务器的无状态连接。
The Web brought some unique challenges to software developers, most notably the stateless connection between the client and the server.
Web向软件开发人员提出了一些特有的挑战，最明显的就是客户机和服务器的无状态连接。
应用推荐