tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajeev Jha <>
Subject Re: Rephrased: Maximum number of simultaneous HTTP connections
Date Tue, 04 Apr 2006 09:51:06 GMT
I think everybody on the list here agrees that http is not the right 
sort of thing for a chat  application. And most  of the IM/chat  
applications  do not  run on  http  anyway. opening the sockets directly 
for such an application is better/easier any day.
However,  people do demand  an  HTTP  end point to  existing 
applications. The big attraction is avoiding any client software, you 
just need a browser.
so finally it is about the availability of an end point in most cases.


Darryl L. Miles wrote:

> Tp wrote:
>> Well, that's a good question. The outcome of this thread might be 
>> just that. But it would have been nice to use existing software 
>> infrastructure.
> Maybe look at the IRC protocol ?   Has existing infrastructure, 
> heritage and eco-system.
> The outline of the protocol is one persistent connection per client, 
> there are a handful of server implementations to choose from which 
> have been optimized to handle in the region of ~10000 socket 
> connections per server generally using few threads (certainly not one 
> thread per connection).  You can scale the system with hooking up 
> servers (daisy chain).  The protocol has been around a bit longer than 
> HTTP and serves a completely different purpose more fitting with your 
> requirements.  The only bad point is no real high-availability plan 
> from the clients perspective (you may loose a fragment of a 
> conversation during server migration), but the server implementations 
> have stood the test of time and are on the whole quite stable.
> Maybe you are trying to use a jumbo jet to fly to the moon with HTTP.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message