[
https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4186:
-----------------------------------------
Ashish, do you have an example of a browser that doesn't cache a resource
representation if it has been retrieved with query parameters? There should be absolutely
no difference between query and path parameters, unless the browser is broken. If you set
the right cache control headers, the browser should cache it locally.
There are still some other (minor) reasons for using path parameters instead of query
parameters, but they are not performance related. (Note that we do not care about
<IE7.)
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