Interesting question, I think that
- when <expiration-cache> tag is set to 0 in portlet.xml, it would make sense that this is the default setting - when expiration-cache > 0, I'm not sure. I guess you could still have this as default, forcing the cache mechanism in the portlet container to be used also when back and forward buttons are used. The drawback would be extra roundtrips for pages where the local cache still is valid. (There is also a META HTTP-EQUIV="EXPIRES" tag, but I'm not sure how well it works on different browsers). See http://www.i18nguy.com/markup/metatags.html for a list of useful metatags. regards jan ole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868645#3868645 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868645 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
