Thanks Filip.
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 03, 2007 6:39 PM
To: Tomcat Users List
Subject: Re: Comet and Async Servlets - Architecture Question
Praveen Balaji wrote:
> Thanks Sebastiaan. I came to about the s
riginal Message
From: Sebastiaan van Erk <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, May 2, 2007 11:19:29 AM
Subject: Re: Comet and Async Servlets - Architecture Question
Praveen Balaji wrote:
The
last few days I have been evaluating using CometProcessor to work like
what we want to use is Async
servlets and Comet is not intended to solve the same problem.
Let's see what I can come up with!
Praveen
- Original Message
From: Sebastiaan van Erk <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, May 2, 2007 11:19:29 AM
Subject: Re
Sorry about this last email. It was for Sebastiaan but in another thread.
Cheers,
Martin
On 5/2/07, Martin Perez <[EMAIL PROTECTED]> wrote:
Sebastiaan,
Yes you're right. I forgot to add something like isClosed() to your
SynchronizedOutputStream so I can check if it's closed before writing.
A
Sebastiaan,
Yes you're right. I forgot to add something like isClosed() to your
SynchronizedOutputStream so I can check if it's closed before writing.
Anyways, I found that after a certain limit (for ex. 6000 -> 8000 users) the
system starts to behave incorrectly. Some clients never get an answe
Praveen Balaji wrote:
The
last few days I have been evaluating using CometProcessor to work like an
Async Servlet for me. I pick up the CometEvent object on BEGIN event and
process the whole request asynchronously. When I am done, I close the I/O
stream.
I
would like to know what the Tomcat
The
last few days I have been evaluating using CometProcessor to work like an
Async Servlet for me. I pick up the CometEvent object on BEGIN event and
process the whole request asynchronously. When I am done, I close the I/O
stream.
I
would like to know what the Tomcat developers and t
