-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick,
On 10/26/2009 9:21 AM, rowlando wrote: > I suggest you read the links I posted if you're interested in the why. Ouch. Maybe /you/ should read your own links: " [Comment from reader "Murray":] I’ve also heard that when using @import, browsers may not cache the css files, unlike with a . But I haven’t been able to verify this. Are you aware if it actually matters from a caching perspective? If so, it might be another reason to avoid @import. [Reply from Steve:] @Murray: I haven’t heard that and it doesn’t happen in my tests. " You're right in that @import appears to serialize CSS fetching in many browsers, and that's bad. On the other hand, why not use Steve's suggestion and use the LINK LINK technique? Presumably you have separate stylesheets for a reason. Why not keep them separate? As usual, I agree with Hassan's suggestion that you map /assets/css/concat/global.css to the JSP servlet and use JSP in your dynamic stylesheet if you've already decided to use JSP. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrls3IACgkQ9CaO5/Lv0PB2aACgj63bdLYJoAfXXygk+Xrgwwju DmAAni0Jgf+A0KFYykaI+3xpAS6Gjeh6 =hvie -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
