<br><br><div class="gmail_quote">On Tue, Mar 1, 2011 at 1:23 AM, John M. Dlugosz <span dir="ltr"><<a href="mailto:wxju46gefd@snkmail.com">wxju46gefd@snkmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Say I want to use TT in the .css, so (for example) I can name my colors and other repeated content easily.<br>
<br>
I'm assuming that I can define a Path of some kind on a rule to serve those. Any recipes to share?<br>
More critically, I want the browser to know that it doesn't have to keep re-fetching it on every view of every page. How would I manage that?<br></blockquote><div><br></div><div>At build time I minimize and compress css and js (and images) and combine into single files grouped by page(s). They could be pre-processed by TT very easily. The final file names include an MD5 of their content forcing a re-fetch only if they ever change. (Maybe HTML5 manifest files will simplify this a bit.)</div>
<div><br></div><div>They get served by Catalyst with an expiration time a year or so into the future. The URL for the resources on the web pages point to a CDN which caches the fetched files. A caching proxy with a different domain would also work. Under development mode the css files are served directly from the Catalyst server as separate files, not minified to make debugging easier.</div>
<div><br></div><div>I've been debating using data URLs for the smaller background images instead of using Sprite files, but support is not great yet.</div><div><br></div><meta charset="utf-8"><div>I thought about using TT for css, but the need has never come up and it would mean more training. </div>
<div><br></div><div> </div><div><br></div><div>-- </div></div>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>