[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Christian Bauer updated JBSEAM-4186: ------------------------------------ Fix Version/s: 2.2.0.CR1 Priority: Critical (was: Minor) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Christian Bauer updated JBSEAM-4186: ------------------------------------ Component/s: Core Remoting (was: Wiki) Testing done on wiki, now finishing implementations for conditional GET/HEAD, gzip content encoding, cache control headers. Still need to actually use them then on improving various built-in Seam resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Christian Bauer updated JBSEAM-4186: ------------------------------------ Summary: Bundle remoting resources as path parameters of interface.js GET request (was: HTTP caching for SeamResourceServlet resources) Component/s: (was: Core) Priority: Minor (was: Critical) This has been a catchall and most of the issue has been resolved: - gzip'ing the content is done by Tomcat if enabled in server.xml - setting the right cache control headers (yes, browsers cache even interface.js?componentName just fine and they are broken if they don't) is the job of the CacheControlFilter in Seam 2.2.1 - improving cache-validation requests with 304 responses can be implemented with ConditionalAbstractResource but it's not as important as the previous two items - bundling several component interfaces into one GET request is what this issue is now about: http://my.host/component1;component2/interface.js -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Ashish Tonse commented on JBSEAM-4186: -------------------------------------- Christian, I wasn't able to properly reproduce this. I apologize for the sidetrack on this issue regarding browsers. It could've just been that the 200 status code that's been fixed by your ConditionalRequest handler was mixed with this assumption. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Christian Bauer reassigned JBSEAM-4186: --------------------------------------- Assignee: (was: Christian Bauer) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira