Getting back to my original question... is there any harm if I make
the front servlet async-supported all the time, even though not all my
application servlets support asynchronous mode?
Thank you!
On Wed, Jul 15, 2015 at 4:55 PM, Rilak Kun kunri...@gmail.com wrote:
Thanks Chris
This is great news. Thank you Mark!
On Thu, Jul 16, 2015 at 1:57 PM, Mark Thomas ma...@apache.org wrote:
On 16 July 2015 21:49:33 CEST, Rilak Kun kunri...@gmail.com wrote:
Getting back to my original question... is there any harm if I make
the front servlet async-supported all the time, even
SIGNED MESSAGE-
Hash: SHA256
Rilak,
On 7/14/15 11:06 PM, Rilak Kun wrote:
Our application is running in OSGi. Servlets are contributed via
Eclipse extension point, so they can be registered in different
plugins without changing the web.xml.
When a servlet is registered, you can map
:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rilak,
On 7/14/15 9:20 PM, Rilak Kun wrote:
I have only one servlet definition in my web.xml. This servlet acts
as a bridge servlet for delegating requests to the actual 50
servlets in my application. I would like to make one of the 50
servlets async
Hello,
I have only one servlet definition in my web.xml. This servlet acts as
a bridge servlet for delegating requests to the actual 50 servlets in
my application. I would like to make one of the 50 servlets
async-supported. I can think of two ways to do it:
1. Create another bridge servlet for
