Not in this case, but the requirements this poses on the back-end system is similar. As explained above, the latency will be high, but so must the throughput.
awarnier wrote: > > keenny wrote: >> Hello all, >> >> I'm currently working on a system that must be able to serve thousands of >> requests per sec. The requests/responses contains only small amounts of >> data >> (ajax XMLHTTPRequests) and are not long lived (connection keep). > > Whenever I see a description like the above, my immediate thought is of > some drop-down box a la Google, with suggested values that change while > the user is typing. Is that the kind of thing you`re talking about ? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/Fastest-method-to-serve-dynamic-java-content-tp22034617p22035537.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
