Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The biggest issue is performance. The
chat's output window requires one open HTTP connection per client. This
means, that when you have 3000 people following the chat that the server
has
NBIO will not help very much ;o) we are running such an application
and want to migrate to apache/tomcat. The issue is, all the
optimizations you hear about are done from the request's side which is
of not much use in this case. The limiting factor would be
* how many connections can you
On 4/3/06, Tp [EMAIL PROTECTED] wrote:
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The biggest issue is performance. The
chat's output window requires one open HTTP connection per client. This
means, that when you have 3000 people
Remy Maucherat schrieb:
On 4/3/06, Tp [EMAIL PROTECTED] wrote:
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The biggest issue is performance. The
chat's output window requires one open HTTP connection per client. This
means, that
