> Is there a weblocks plan for either: > > 1) versioning css/js files so we can get clients to permanently cache > files > 2) consolidating files in some way so they're both minimized and > combined?
Yes, both: http://weblocks.lighthouseapp.com/projects/18897/tickets/7-dependency-bundling Someone volunteered to do this but so far I haven't seen results. I'll ping him. > I was thinking about doing deployments using apache rewrite rules to > do versioning - my app generates versioned URLs, apache rewrites them > to the common name and then I just increment apache rules and weblocks > versioning when I upgrade a public site with changed js/css files. I don't like this. For me the big plan is to fully get away from static files and generate all CSS and JS in Lisp (using static files only as an option)*. I do think that better optimized web servers like Apache have an edge over Hunchentoot, but I also think that it's negligible for most purposes as long as we support bundling. Leslie * http://weblocks.lighthouseapp.com/projects/18897-weblocks/tickets/17-dynamic-css-generation#ticket-17-2 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
