Hello,
I'm trying to figure out the optimal way to deal with caching and out of
date resources and can't really find which methodology to adopt.
Considering that:
a) css and js files are only accessed from web pages
b) image files are accessed from web pages and from email clients (links
stored for a long time)
c) image files are referenced from css (e.g. background-image url)
d) font files are accessed from web pages and maybe eventually from
email clients
e) some css files currently use "@import" statements to include other
css files (this could be removed if needed)
f) css, js, fonts and images currently are all located in the webapp
folder (i.e. I wasn't able to access them with PackageResourceReference)
g) whatever the approach, it needs to be compatible with eventual usage
of CDN services
Questions:
1- Which files should be versioned?
2- Should they be versioned using Wicket's ResourceReferences?
3- Are there other considerations I haven't thought about?
4- Which successful approaches are in use now by other Wicker users?
Thanks for your insight!
Regards,
Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
