"Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote in message
news:99c8b2929b39c24493377ac7a121e21f96cb817...@usea-exch8.na.uis.unisys.com...
From: Bill Barker [mailto:billwbar...@verizon.net]
Subject: Re: Tomcat threads
basically the request is handed off to another thread and the
original one returns to the pool. This also allows for two-way
communication instead of relying on polling.
What's required on the client end? You can't simply push HTML or other
content to a browser. Is a specialized (or at least scripted) client
required?
Mostly useful for custom clients channeling under HTTP, but you could
probably write a scripted client as well that works with it (haven't tried).
The examples in Tomcat 7 are mostly server-push (e.g. fake stock ticker,
chat). These are done by not completing the connection, and just pumping
more data to a chunked response (so you get the spinning wheel the entire
time the apps is running). They work in most browsers (only most, because
I've only tested them in IE and FireFox).
But as I said before, would probably help the OP, assuming that traffic
isn't too great.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org