Hey Guys,
It has been my assumption that Tomcat 7's comet implementation (ie,
asyncSupported=true), will automatically use NIO processing.
Is that not true? Do I need to set the connector to be
org.apache.coyote.http11.Http11NioProtocol explicitly?
Thanks,
Matt
On 08/11/2011 20:15, Matthew Tyson wrote:
> Hey Guys,
>
> It has been my assumption that Tomcat 7's comet implementation (ie,
> asyncSupported=true), will automatically use NIO processing.
Comet != Servlet 3.0 async
> Is that not true?
Yes, that is not true.
> Do I need to set the connector t
I guess what I'm asking is if I just start using the Servlet 3.0 support
for suspending requests out of the box, will it be a thread blocking
implementation I'm using?
HTTP APR/native is blocking as well, correct?
So if I want to use Servlet 3.0 async (eg, a call to request.startAsync),
and have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew,
On 11/8/11 4:43 PM, Matthew Tyson wrote:
> So if I want to use Servlet 3.0 async (eg, a call to
> request.startAsync), and have it be handled without blocking IO, I
> need to use the NIO connector?
To repeat Mark's reply:
> On Tue, Nov 8, 2
Matthew Tyson wrote:
>I guess what I'm asking is if I just start using the Servlet 3.0
>support
>for suspending requests out of the box, will it be a thread blocking
>implementation I'm using?
That depends what you mean by "thread blocking". Once startAsync has been
called the thread that was p
That's very illuminating, thanks.
I was looking at the table at the bottom of
http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html#NIO_specific_configuration,
and got the impression APR was blocking also, but now I see 'waiting for
next request' is non-blocking in the TC7 table.
Would you give
