On 4/3/06, Rajeev Jha <[EMAIL PROTECTED]> wrote: > Tp wrote: > > And there seems to be no workaround, because the connection will close > > after the doGet() and doPost() method finishes (is that actually > > true?). So, the only way to keep 3000 simultaneous connections is to > > keep 3000 of those methods from returning, wehich means keeping 3000 > > threads busy. > > You can try jetty 6 also [ if you are not very particular about using > tomcat ] . Jetty 6 Continuations can help you do a suspend/resume of > request. so a thread is not blocked due to idle wait and you can > multiplex more connections on less threads.
The hype friendly "continuation" name has no business being associated with this particular feature, since the said feature is not continuations (which is a fancy - and IMO forward thinking and actually useful - programming model for implementing the often seen multiple HTML form "wizard" style process - and of course, which is going to use one HTTP request per form, as usual), and is also quite useless. If all you need is to reinvoke the service method once there's more input data available, you can just as easily use multiple small requests (over a kept alive connection), which is equally cheap in terms of processing and allows not breaking the HTTP and Servlet API designs. The real problem, and the actually useful capability (especially for a big chat room like is the case here), is to be able to output data asynchronously (= without polling). -- xxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Developer & Consultant JBoss Inc xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
