-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23/03/2014 22:07, Christopher Schultz wrote:
> Mark,
> 
> On 2/27/14, 12:56 PM, Christopher Schultz wrote:
>> Mark,
>> 
>> On 2/25/14, 3:31 AM, Mark Thomas wrote:
>>> 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.
>> 
>> Okay, thanks.
>> 
>>>> 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.
>> 
>> That's what I was thinking. Thanks for confirming.
> 
> Another quick question: during the sim-blocking for reading the 
> request-body, does the request go back into the poller queue, or
> does it just sit waiting single-threaded-style? I would assume that
> latter, otherwise we'd either violate the spec (one thread serves
> the whole request) or spend a lot of resources making sure we got
> the same thread back, etc.

Both.

The socket gets added to the BlockPoller and the thread waits on a
latch for the BlockPoller to data can be read.

Mark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIbBAEBAgAGBQJTL1xiAAoJEBDAHFovYFnnJGcP9jBIyVGXlYL8pSVMzMNvf1dd
t6d66bajcWMTINmnCcXOzowdnBpDQHyIPKaS0U7RjmBpbOGrK0r+rfVBqkFNPcPR
J9ivXJeZHHgRFVHFyfanBKUwWGGYcFKQuLBfd9vzai2bAyX3/Le0NvZc0/c+/PAA
FPJPDVOUNtN57GKUa+VWJ0Hm7U9YH1VufcvNp/ULNnzkeeg0pnpa8aXroxdtMqw2
j65K3C9O8EQyYU3AzcVMlaxmP+0bGyhCBK3gWb/ZXAh2+0E/14zrBKVqNnRjxo8c
zAPjN79BY+xQ6Un4gEb/XInPFekUlh+IQRSQy7IZ9gmHAmfF/HQ73fEMyS5D6QJ4
Ezs8+K56QniZLE2funSvHX3VWCUyqh/lCYMi0u8RuZw7xOrwsKVK37pmPpk8xDAc
jWcKASOaA4nLDOypb8ys7KNhZSMWLxwcIyLTT8Ck7BDX4PWrE3bPly2cJ2GAkd4v
slRLMuoddMziKgG0dJyi4lpMkR4FQPU1NVS8d+ohoUccfbYSVNM3cLPCOeVJjdeC
ywvhVgKvUItESvuOuhTdyx/sYjA6UJ9bWl1esYh6CVBFQqpnTIsK499ORqJGcosI
N6l2XBIiRhvW3EuF1moppYXX6rUtCz8m+9MWmlpiB6TSU6bI9fu48xFx0JvoN+dD
jruU5ZNKVlRYAYbIh+Y=
=21mp
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to