Consider: Implement ETags in Shindig
------------------------------------
Key: SHINDIG-1350
URL: https://issues.apache.org/jira/browse/SHINDIG-1350
Project: Shindig
Issue Type: New Feature
Components: Java
Reporter: John Hjelmstad
Shindig's services do not utilize ETags.
The primary rationale has been that the gadgets/OpenSocial environment largely
involves tightly controlled URLs. For instance, server-generated proxy URLs may
contain a v=<version> parameter, in the (accurate) presence of which a resource
is served with a 1-year cache.
However, the proxy in particular is often used in situations where URLs are not
server-generated. The most obvious example is gadgets.io.getProxyUrl(...).
Supporting ETags for these seems quite sensible, as it would save bandwidth.
Further, due to the buffered nature of Shindig's HTTP Fetcher pipeline, and the
fact that Version information is available through the UriManager.Versioner
pattern, it would be trivial to support this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.