You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Dan Becker (JIRA)" <de...@tuscany.apache.org> on 2008/08/24 23:51:44 UTC
[jira] Updated: (TUSCANY-2516) HTTP binding should support etag and
if-modified headers
[ https://issues.apache.org/jira/browse/TUSCANY-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker updated TUSCANY-2516:
--------------------------------
Attachment: TUSCANY-2516.patch
Contains full implementation of HTTP binding cache support (ETags LastModified) on GET, PUT, POST, DELETE operations.
32 new unit tests have been added. Run with HttpBindingCacheTestCase JUnit test.
> HTTP binding should support etag and if-modified headers
> --------------------------------------------------------
>
> Key: TUSCANY-2516
> URL: https://issues.apache.org/jira/browse/TUSCANY-2516
> Project: Tuscany
> Issue Type: Wish
> Components: Java SCA Misc Binding Extensions
> Reporter: Jean-Sebastien Delfino
> Assignee: Dan Becker
> Fix For: Java-SCA-Next
>
> Attachments: TUSCANY-2516.patch
>
>
> The HTTP binding currently does not support etag and if-modified headers for implementation-resource and implementation-widget components, preventing Web browsers to do any caching.
> Supporting etag and if-modified should be easy for the above component implementation types, just a matter of calculating a checksum and use it as etag or checking the timestamp of the served file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.