(A) Biggest issue: My (mis)understanding that comet sufferred from the
'one connection/one thread' problem.
I see from Kris Zyp's response on http://cometdaily.com/2007/12/10/comet-gazing-scaling/
that with the Tomcat
comet interface, this is decoupled, so that the number of connections
can
Oscar wrote:
We used BlazeDS's publish/subscribe feature to implement server-side PUSH.
However, we found it didn't work well with NIO, CPU wasn't stable, What's
even worse, CPU will constanly be 99.9%.
The system worked well with APR.
Is this just with Tomcat or did you investigate with somet
We used BlazeDS's publish/subscribe feature to implement server-side PUSH.
However, we found it didn't work well with NIO, CPU wasn't stable, What's
even worse, CPU will constanly be 99.9%.
The system worked well with APR.
We're looking into NIO-related code in tomcat's latest codebase.
Anybody k
Ken Bowen wrote:
Hi All,
I'm working on a project which has developed a need to push data from
the server to browsers.
In the short term, the numbers of browsers will be moderate, but in
the long term, it appears
that we will need to scale up to very large numbers, so the 'one
thread per conn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken,
I don't know anything about the use of NIO or server-side push, but...
Ken Bowen wrote:
| 2) Is there any analogue of Jetty 6 Continuations available in Tomcat?
| They sound like a good mechanism
| for this problem. Does anyone on the list hav
Hi All,
I'm working on a project which has developed a need to push data from
the server to browsers.
In the short term, the numbers of browsers will be moderate, but in
the long term, it appears
that we will need to scale up to very large numbers, so the 'one
thread per connection' issues
