[
https://issues.apache.org/jira/browse/SHINDIG-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682855#action_12682855
]
Kevin Brown commented on SHINDIG-954:
-------------------------------------
DefaultGadgetSpecFactory intentionally ignores HTTP response headers in all
cases, because there is no standard way to override them. This change would
cause most gadgets to be re-fetched far more frequently than is appropriate, to
the detriment of both the end user and the gadget developer.
There is no difference between "cache time" and "forced cache time" in the
HttpRequest object, so the change here is essentially a no op. We generally do
not honor HTTP request headers, because an HttpRequest object does not
represent a request from an end user.
Lastly, this patch doesn't actually do what the description claims it does.
EhCache will still use the TTL that is configured in the cache.conf file after
you apply it, because the EhCache wrapper only stores String -> Object
mappings, and is not aware of any per-object type differences.
> Shindig does not recognize Response Headers for Cache TTL
> ---------------------------------------------------------
>
> Key: SHINDIG-954
> URL: https://issues.apache.org/jira/browse/SHINDIG-954
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: trunk
> Environment: OS: Windows XP / Solaris
> Server: Weblogic
> Reporter: Tamil Ramasamy
> Attachments: patch_SHINDIG-954.zip
>
>
> It looks like the cache headers of HTTP requests are not considered for
> EHCache Cache TTL. However, it is being captured in
> org.apache.shindig.gadgets.http.HttpResponse, using method getCacheTtl() and
> getCacheExpiration();
> Please fix it for better usage of Ehcache. Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
