the file last modified time is by far the most standard and "correct" solution.
On 9/18/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
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_.
so why would you not want to cache resources from the wicket jar? they dont change every week like your app. if you are using some other 3rd party custom wicket component that are in their own jars why do you want to reload those resources as well if they havent changed?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?
because _javascript_ libs can be huge and it will make your site slow if the user has to pull them down on every request.
-Igor
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
