2014-02-25 12:31 GMT+04:00 Mark Thomas <ma...@apache.org>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 25/02/2014 06:03, Christopher Schultz wrote: >> All, >> >> I'm looking at the comparison table at the bottom of the HTTP >> connectors page, and I have a few questions about it. >> >> First, what does "Polling size" mean? > > Maximum number of connections in the poller. I'd simply remove it from > the table. It doesn't add anything. > >> Second, under the NIO connector, both "Read HTTP Body" and "Write >> HTTP Response" say that they are "sim-Blocking"... does that mean >> that the API itself is stream-based (i.e. blocking) but that the >> actual under-the-covers behavior is to use non-blocking I/O? > > It means simulated blocking. The low level writes use a non-blocking > API but blocking is simulated by not returning to the caller until the > write completes.
s/Sim/Simulated/ on the page > >> It is important to make that distinction since the end user (the >> code) can't tell the difference? > > The end user shouldn't be able to tell the difference. It is important > and it indicates that there is some overhead associated with the process. > >> Unless there is another thread pushing the bytes back to the client >> for instance, the request-processing thread is tied-up performing >> I/O whether it's doing blocking I/O or non-blocking I/O, right? > > Correct. (excluding sendFile, async, WebSocket, Comet) It is worth adding those four (sendfile etc.) as rows into the table. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
