Hi,
I'm trying to make the use of CDN hassle free with my Wicket Apps.
.. where *IF* a CDN location is specified then all paths like
.. become
This applies to JS, CSS, and img tags mainly.
Am wondering where the best place to automate this would be ?
1. Build Process; do a REPLACE during production BUILD
2. Wicket code that loads using IResourceStream UrlResourceStream(url) ;
Intercept the raw HTML stream and re-generate it? (if this is cached may be
efficient??)
3. HttpServletFilter --> Just before its passed back from the Web Server. Do
a RegEx scan and replace (Maybe too inefficient , but less intrusive to any
Wicket Vodoo)
Thoughts?
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!
I'm trying to make the use of CDN hassle free with my Wicket Apps.
.. where *IF* a CDN location is specified then all paths like
.. become
This applies to JS, CSS, and img tags mainly.
Am wondering where the best place to automate this would be ?
1. Build Process; do a REPLACE during production BUILD
2. Wicket code that loads using IResourceStream UrlResourceStream(url) ;
Intercept the raw HTML stream and re-generate it? (if this is cached may be
efficient??)
3. HttpServletFilter --> Just before its passed back from the Web Server. Do
a RegEx scan and replace (Maybe too inefficient , but less intrusive to any
Wicket Vodoo)
Thoughts?
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!