Tim Funk wrote:
yes and no. The browser makes a request to apache. Then the request is proxied to tomcat. When the servlet has been served, the browser issues a keep-alive and reuses the apache socket connection to get any other assets (such as images) needed.
2 requests, one connection.
With the numerous speed improvements in tomcat 4.1 and 5 - there might not be much (if any) difference in speed for a low (relative term) volume site.
You'll need to load test to see how things scale.
-Tim
[EMAIL PROTECTED] wrote:
I am working on a servlet that will be served from tomcat which is
connected to apache. Currently I have the servlet being handled by
tomcat, and the image handled by apache.
Won't this require 2 get requests by the browser? One being the image,
and one being the servlet?
Unfortunately, this is an SSL protected site and none of the pages are
cached. So my question is, what is the best approach with performance in
mind? What is the fasted way to get the image and dynamic HTML back to
the browser ?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
