why does it matter if html is cached? you already said its all the same. as far as css resource caching, the theme name is in the url to the css resource as per your example, so once again why does it matter if its cached?
-igor On Fri, Apr 9, 2010 at 10:07 AM, Apple Grew <[email protected]> wrote: > Hi All, > > I am trying to create a themable wicket application which has one html per > page but different CSS files to change its looks. The CSS files are > referenced in the <head> of the html. The CSS files have been named as - > <theme_name>-all.css. I am very well able to dynamically generate the CSS > urls based on the theme name. The theme names are fetched from session, as, > MySession.getThemeName(). > > My concern is, that Wicket might cache the generated html file. So even if > the theme changes at runtime, the html with old CSS names will be served. > Furthermore, each user can have different themes, but here we have only > html. > > If my understanding is correct then I should set the style to the theme > name. I read somewhere that Wicket generates keys to reference the cached > resources. So, I am guessing, that user A tries to access Home.html with > 'classic' style then Wicket will render and cache that page as (say) > classic-Home. Now, if user B tries to access the same page but with style > 'jazzy' then Wicket will use another key to store cache. > > I am simply guessing. Am I on the right track? Will this work? > > Regards, > Apple Grew > my blog @ http://blog.applegrew.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
