So... that's one argument. The performance gain you can get by using a HTTP server can be considerable on heavy loads, though containers like Resin tend to be allmost as fast at this as Apache - which still can beat all competition afaik.
But... this is not the drastic gain. *The* drastic gain is - like Johan's example - to let the browser know the image/ resource can be cached. You do that by tweaking 'getLastModified' and setting cache control headers. However, that will only work for requests that look the same (have the same URL). Our's don't, because we have that render count parameter (amongst others). So we should somehow be able to convert the resource url's to 'static' ones. Dunno how (yet).
Eelco
Gili wrote:
<Gili presses the reset button>
Ok, it seems either I was misunderstanding what was being said or you misunderstood me so lets get back to the beginning.
I am saying that the Wicket servlet should handle image
requests and decide whether or not to retrieve them from the static
image store (i.e. normal paths) or dynamic image store (i.e. tempdir
cache directory). I don't agree/understand why Eelco says that it is
not possible and that the Webserver needs to do something on our
behalf...?
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
