Web servers that have been designed so that each concurrent connection requires its own process are not scalable for real-world applications; at least, not without help.
Web服务器已进行了相应的设计，要求每个并发连接都无法针对实际的应用程序调整自己的进程；至少在没有帮助的情况下无法进行此调整。
These are limited resources as well, and having too many concurrent requests may cause failures, such as failure to allocate a JDBC connection.
这些也都是有限资源，有太多的并发请求也可能引起失效，例如不能分配JDBC连接。
Since each thread performs a task, each concurrent thread needs a database connection.
由于每个线程都需要执行一个任务，因此各并发线程都需要一个数据库连接。
There can be no concurrent users (the application has exclusive access to the database files), but there are no additional threads nor TCP connection overhead.
不能存在并发用户(应用程序独占地访问数据库文件)，但因此也没有额外的线程和TCP连接开销。
If a server anticipates handling a very high number of concurrent clients, the server can post a single zero byte receive on each connection.
如果一个服务器能够预先估计可能会产生的最大并发连接数，服务器可以投递一个使用零缓冲区的receive在每一个连接上。
In this case, the listener port's ConnectionFactory needs to support only one connection, but it must allow one session for each concurrent MDB.
在这种情况下，侦听器端口的ConnectionFactory只需要支持一个连接，但是它必须允许每个并发m DB都有一个会话。
For example, you might be testing ane-commerce site that has an Internet front-end used by hundreds of concurrent customers coming in over many connection speeds and using different browsers.
例如，您可能针对数以百计的客户同时透过许多连接速度，并且使用不同浏览器连接至具有网际网路前端之电子商务网站进行测试。
For example, you might be testing ane-commerce site that has an Internet front-end used by hundreds of concurrent customers coming in over many connection speeds and using different browsers.
例如，您可能针对数以百计的客户同时透过许多连接速度，并且使用不同浏览器连接至具有网际网路前端之电子商务网站进行测试。
应用推荐