On Wed, 05 Jan 2005 00:06:18 +0100, Eelco Hillenius wrote:
>Because in the ideal case, you would have a servlet engine (Jetty,
>Tomcat, Resin, Websphere) for running Java code and serving the results
>and a webserver (Apache, IBM Http Server) for serving static content
>like images.
>
>Eelco
>
>Johan Compagner wrote:
>
>> Why should the server have direct access to it?
>> How do you think that currently static resources that are served by
>> tomcat/resin or jetty? Through a servlet!
>> It is just a way that you set the right headers AND return the right
>> date in the getLastModified() method of a servlet..for a specific
>> request..
Ok, I follow you so far, so why does this prevent us from
serving up dynamically generated images from tempdir? I'm guessing
you're only objecting to the idea of serving up static images using the
servlet as opposed to using the webserver? I'd just like the ability to
dump my static images into the WebApp directory. It would be an option,
nothing else. There is nothing preventing us from dumping the static
images into another directory that the webserver can get at directly,
right?
Gili
-------------------------------------------------------
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
