Bundling, versioning, etc is cool. Thanks! Versioning works great if you're doing interactive updates on a running site, but the default counter variable is reset if you have to restart or you do a full upgrade of the site (or for some reason lose your tally file state). Setting *initial-bundle-id* on a recover or significant upgrade feels likely to be error prone.
Another approach might be to have both a release version associated with the webapp "1.1". If you ever delete the tally file, you can simply increment your site version to ensure that resources are freshly cached. (setf (webapp-version webapp) "1.1") => weblocks.1.1.0.js were the last number is the current tally. Anyone have a better (or existing) solution to this problem? It's a simple patch but I don't want to step on toes. Thanks, Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
