Guillaume Delhumeau wrote:
Note also that a LESS resource can contains Velocity
code, so some parts
can be dynamic (ex: a color which depends on the wiki id).
I've met this claim
on a steady basis since quite some time, e.g. using
the /skin/ URLs, and dare say that this is ruining normal caching based
optimization (e.g. on Apache or CloudFront).
If there's something dynamic in the CSS or JS it should really be
requested separately from the mass (and probably not need LESS).
paul