[
http://jira.amdatu.org/jira/browse/AMDATU-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10294#comment-10294
]
Marcel Offermans commented on AMDATU-82:
----------------------------------------
So we have a collection of URLs, and we currently fetch the content of each,
every time a user views for example the available gadgets. So I don't see how
we can do more than rely on the HTTP caching headers here. We don't own those
resources, so the provider is the only one who can tell us if and how long we
can cache them. That is, unless we completely ignore the HTTP protocol and
simply cache resources, which would not be my preferred solution.
Therefore, I agree with your comment that the best we can do here is use a HTTP
client library that supports accessing the HTTP caching metadata to determine
if our cached version is still current. It is probably also the best solution
for concurrently fetching multiple requests (and detecting stale ones). On top
of that we can then build our cache.
> Loading of gadget definitions is very slow
> ------------------------------------------
>
> Key: AMDATU-82
> URL: http://jira.amdatu.org/jira/browse/AMDATU-82
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu OpenSocial
> Affects Versions: 0.0.4
> Reporter: Dion Meijer
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.0.6
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
