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
what else I could synchronize on.
If anybody knows a better approach, I would like to know. :-)
Regards,
Sebastiaan
Martin Perez wrote:
Hi,
Thanks for the tip Sebastian, but it doesn't work for me. I added your
class, wrapped all the output streams and synchronized close events
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
whenever I called event.close() on the Comet event
(especially in the READ event). When doing serveral IO operations on the
output stream which should not be interrupted, you can simply
synchronize on it (since SynchronizedOutputStream locks on itself).
Regards,
Sebastiaan
Martin Perez wrote
Hi all,
I have been testing Tomcat comet support during the last days. I've created
a test application that simulates data streaming to multiple clients.
Clients open a connection to the server and the connection is hold open. In
the server there are several sender threads that leverage comet
On 4/28/07, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
Hi,
The request, wait, async response + close pattern seems to be a
pretty common use case though, especially with server side push
(AJAX), so it would still be good to have a solution that works well
allways.
Yes, and for this you
Hi,
For the activity seen in the last weeks it seems definitely clear that Comet
is hot topic.
Anyways, I've been playing now for some days with Tomcat 6 and Comet. No
substantial tomcat related problems as far as I know, so great job.
My scenario is quite simple. A desktop application opens a
for being a great implementation.
Regards,
Martin
On 4/24/07, Rémy Maucherat [EMAIL PROTECTED] wrote:
On 4/23/07, Martin Perez [EMAIL PROTECTED] wrote:
Any suggestions?
I would try to avoid using directly Object*Stream, to see what
happens, and verify the validity of the data which is sent
