[
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
Bundle remoting resources as path parameters of interface.js GET
request
------------------------------------------------------------------------
Key: JBSEAM-4186
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4186
Project: Seam
Issue Type: Feature Request
Components: Remoting
Reporter: Christian Bauer
Assignee: Christian Bauer
Priority: Minor
Fix For: 2.2.1.CR1
Attachments: restful-remoting.diff
This affects built-in Seam stuff like the remote.js that is always delivered with 200 OK
and can be quite large. We need to explore how/when we can send 304.
I've assigned this to the 'wiki' component because I want to try different
solutions there first.
--
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