That would be the last go. Trying to figure out if there is techniques to handle such scenarios. Looks like comet can asynchronously push data to the user. If this is going to be seamless to the client, it might as well look like a response for their request.
On Wed, Mar 3, 2010 at 9:25 AM, Mark Thomas <ma...@apache.org> wrote: > On 03/03/2010 17:21, Bharath Vasudevan wrote: > > Hi Charles, > > > > Let me explain the scenario. When tomcat gets a request, it does a socket > > send to some other process to handle the request and then respond. This > > would happen fast. But assuming 20k client requests come in at the same > > time, the server would try to allocate 20k threads and handle it. Mostly > the > > system would trash and go down. > > > > But if it was to be handled gracefully, we can have the threads pick up > the > > request throw it in a queue and let the worker threads work and respond. > Let > > me know if I am missing something here. > > Like the fact that Tomncat is open source and you could just look at the > source code for the various connectors and figure this all out for > yourself? You don't even have to read the source. The connectors > documentation covers this pretty well. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
