The asyncweb API is quite different from this approach - and is much less
servletty.
Maybe take a look at the API and see what you think?
All the Java docs are contained in the current release available here:
https://svn.safehaus.org/repos/asyncweb/release/
Dave
-Original Message-
Interesting article Of course, he missed one other existing
implementation: http://asyncweb.safehaus.org
If you're thinking of getting async services built in to Tomcat, I'd
certainly be interested in jumping on board :o)
D
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Is someone going to get this kicked off.???
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 10 January 2006 12:50
To: tomcat-dev@jakarta.apache.org
Subject: [sales #595323]: test
Dear Mark/Space Customer,
Thank you for your email to our sales
Developers List'
Subject: RE: [sales #595323]: test
PLEASE :)
-Original Message-
From: Irving, Dave [mailto:[EMAIL PROTECTED]
Sent: 10 January 2006 12:52
To: Tomcat Developers List
Subject: RE: [sales #595323]: test
Is someone going to get this kicked off.???
-Original Message
Hi,
Im currently prototyping a NIO connector for tomcat - using tomcat
5.0.28 as a base.
This is to solve a specific issue: We have to support a very high number
of concurrent connections in a high latency server - and want to remove
the thread per connection dependency.
In particular, for my
Remy Maucherat wrote:
A thread will still be needed to run the servlet, so I hope the amount
of time
spent in the service method will be lower than 15 seconds. Otherwise,
there's
no real solution besides having a large amount of threads.
Yeah, that's the crux of it I suppose. Do you know
Remy Maucherat wrote:
I think the conclusion is that your requirements are outside the use
cases for which
the servlet API was designed for, so besides reusing portions of the
code, most of
your request processing cannot quite run inside the main servlet
container.
Yes - and after doing a
