Adam, you are totally right that the 304 mechanism may be working.
The point is, that the resources are returned with a Expires header that is set to Last-modified. That means the Expires date is always in the past. Thus the browser immediately expires the resource and does not even try to use a If-Modified-Since. Therefor a slight improvement would be leaving the "Expires" headers away. It would be even better if Expires would be set to "request-time + some hours". Alternatively just a Cache-control max-age header.
Cheers!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143890#4143890
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143890
I have done the following renaming that will affect versions of JBPC after 2.0.0.CR2:
WindowNavigationalState -> PortletWindowNavigationalState
PageNavigationalState -> PortletPageNavigationalState
Event -> PortletWindowEvent
the reason is that those term were not precise enough and are conflicting with terms in 2.7 core.
JBoss Portal 2.7 WindowNavigationalState is more broad and PortletWindowNavigationalState of JBPC controller is window navigational state for a portlet window.
Note that renaming can easily be done with Idea which has a function to migrate class names.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143862#4143862
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143862