if you're looking for better client performance I would explore other areas first.
1. use gzip compression - this can reduce the html to 1/10th the size. your mileage will vary. 2. caching results on the web-tier 3. putting the images on a dedicated image server 4. distributing your servers across multiple ISP. many service providers don't tell you this, but often their pipe is saturated and can't really handle a large number of concurrent requests. if you host your own servers i would recommend getting more than 1 connection and use different providers Most browsers today are Http1.1 compliant, which means they are limited to 2 connections to the same server. Normally the browser will use the same connection to get the html and the other resources like images and javascript. Are you worrying about images? if that is the case, setup a dedicated image server using apache. you'll easily double the performance of your servlet pages, since tomcat won't have to serve up static content. Plus, it's easier to update the images for the entire site. Rather than copy all the files to every single webserver, you just update the image server and it's done. peter On Fri, 29 Oct 2004 18:01:29 +0200, Andrew Miehs <[EMAIL PROTECTED]> wrote: > Hi Peter, > > I am not using keep-alives to keep session persistence, but was rather > hoping for better client performance. Using keep-alives saves creating > a tcp connection for each request - and thereby saving 3 tcp packets > (and roundtrip times) per request. > > Andrew > > On 29.10.2004, at 17:53, Peter Lin wrote: > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
