[
https://issues.apache.org/jira/browse/SHINDIG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575607#action_12575607
]
Graham Spencer commented on SHINDIG-48:
---------------------------------------
My thinking on this issue is that we can cap the maximum refresh time at 1
hour. For developers who don't change their headers, that should give
approximately the same behavior as what we have today. This feature is really
intended for advanced developers who want to tweak headers to cause their
gadget to refresh more frequently. (An alternate approach is to allow
developers to explicitly invalidate a container's cache, but this doesn't scale
well with lots of containers.)
> Should obey caching headers when fetching XML spec files
> --------------------------------------------------------
>
> Key: SHINDIG-48
> URL: https://issues.apache.org/jira/browse/SHINDIG-48
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Graham Spencer
>
> The original gadget server at google.com would only retrieve gadget.xml files
> once every hour. This makes is hard for app authors to control the deployment
> of their applications.
> Shindig should obey standard HTTP caching headers. This will allow app
> developers to control how frequently their XML files are refreshed. For
> efficiency, there should be a configurable minimum refresh time that allows
> Shindig to compensate for improperly set headers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
