On 9/18/06, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
> Ok.  I'm done here....this is going nowhere, and I guarentee I'm not the
> only one out there that has run into this issue.  It's too bad that this has
> turned into a mud slinging contest.  The Rails team is obviously much more
> understanding of these issues and how to solve them.

Thing is though, is that usually you want images, javascript files and
css and such to be cached, but just not when developing. The
exceptional cases are things like dynamic images and javascript. I
think a setting that would guarantee non-caching for development but
that relies on default behavior in production mode would be best.

What do you think?


Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
Wicket-user mailing list

Reply via email to