You might change your production system every week, others might have release cycles of 6 months. I've seen js files being 200k and more, why should I want to load them again and again with every request? I understand it makes sense for development, but for production?
Igor mentioned it is just 5 lines. Why not make it default for development and allow a component attribute to make it allways non-cacheable. Juergen On 9/18/06, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > > > On 9/18/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > 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? > > Eelco > > > > I work on an application that undergoes weekly production releases, so > we've had to implement something very similar for both development and > production modes. There's just too high of risk if the user gets an out of > date version of the javascript. > > The question is, what is the cost of having these two modes seperate? > keeping everything uniform makes debugging and troubleshooting easier as > well as having only one codebase to worry about. Why not *always* have this > behaviour? > > > > > ------------------------------------------------------------------------- > > 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 > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > ------------------------------------------------------------------------- > 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 > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------------------------- 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 http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
