Hello,
Your posts helped a lot. Thanks everybody!
Now I have a production level asynchronous servlet (a Santa Claus'
gift?), and I want to share some technical learned lessons:
- You must ensure the response be commited before asynchronous writes,
say on the BEGIN event, as said Filip and
ffd wrote:
I found the origin of the problem in my case. The problem was neither the
synchronization nor the connection gone. It was that the asynchronous
writing started too early, before the connection was completely established,
speaking losely...
just call response.flushBuffer() on the
PROTECTED]
--
View this message in context:
http://www.nabble.com/Comet-servlet-synchronization-and-flush-problems-tf4850825.html#a13955206
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new
this message in context:
http://www.nabble.com/Comet-servlet-synchronization-and-flush-problems-tf4850825.html#a13957675
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users
a NPE probably has nothing to do with synchronization, more like you are
trying to write back on an invalid connection (that probably timed out)
Filip
Leonardo Fraga wrote:
Hello,
I'm developing a java web application for finances quotes' real-time
stream, for hundreds of concurrent users.
Hello,
I'm developing a java web application for finances quotes' real-time
stream, for hundreds of concurrent users. The solution involves a long
http request serving javascript snippets that will be executed by broser
when received, changing the data shown to the user.
To do this, I have
