Hello XWiki friends,
Considering files as being "static resources" within an installation
has the big advantage that it can be left to a serving infrastructure
that can honour all the optimized change management the web has
prepared for us (If-Modified-Since, caching at several levels, pre-
allocations thanks to Content-Length...).
I had done it for
http://i2geo.net/, basically by guessing, and the
result was amazing, a huge speed-up perception factor. But now... I
need to redo this for our curriki instance.
How could I recognize a file as being subject of static serving?
- a picture file (pretty clear)
- a css or javascript that does not contain either a groovy or
velocity mark?
There are many examples of the second sort, e.g. all the gwt output
files, but I would like to be sure of them:
- is groovy-inside CSS or JavaScript ever done? (I've never seen it)
- what are "all the marks" of velocity? ( would \#[a-z]+ and \$[a-z]+
be regexps that would suffice?)
thanks in advance
paul