[
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.
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