app server = (AS) struts server = (SS)
req = request
--> = pass
res = response
You lost me here already... What's the difference between the app server and the struts server? Isn't Struts running IN your app server?
With ResourceAction ___________________________________________ First case HTML = req (AS) res (AS) = 2 Second image JPEG (say) = req (AS) --> res (SS) = 3 ..... Tenth image JPEG (say) = req (AS) --> res (SS) = 3
WIthout ResourceAction ___________________________________________ First case HTML = req (AS) res (AS) = 2 First image JPEG (say) = req (AS) res (AS) = 2 Second image JPEG (say) = req (AS) res (AS) = 2 ..... Tenth image JPEG (say) = req (AS) res (AS) = 2
This is 22 versus 32. Apparently you "forgot" (I think?) that the app server has to handle ten images too. They don't just go out with the page, although we are looking at this in a very oversimplified sense.
I don't see how you got 22 OR 32! :) The first request from the client is for the HTML document, right? So that's one request. The browser then sees ten <img> tags, regardless of what they point to. So for each one it makes a request. That's 10 requests, right? So it's 11 in all from the client to the "server" (ignoring for the moment whether "server" means app server alone or web server in front of app server, or whatever other configuration you might dream up).
The only different between the two approaches we've been discussing is what on the "server" is going to handle each of those 11 requests... Is it a web server sending back a static HTML page for the first request, and then an image for each of the subsequent 10 image requests, or is it a web server returning the HTML page and then an app server returning the images, or an app server returning the page AND the images?
There is no question that the AS is quicker with HTML than the SS, but I am not so sure about the images. The SS may be faster. There is lots of room here for tuning.
Let me ask you this question... If you are accessing a web site, and you connect "directly" to the Internet, is that, ignoring things like caching and such, generally going to be faster than going through a proxy? I'd hope you would say yes. Now, clearly, if the proxy is doing caching and/or other optimizations, it might turn out to be faster, but that further proves my point: the web server is like the proxy in this example.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
