[
https://issues.apache.org/jira/browse/SHINDIG-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676608#action_12676608
]
Pan Jie commented on SHINDIG-943:
---------------------------------
About Limited invalidation, here're my thoughts:
1. Caching happened in 2 places: stuff needed by gadget rendering(including
gadget specs, gadget message bundles), and stuff fetched by makeRequest.
2. All these stuff are cached when fetching, aka, BasicRemoteContent->fetch().
3. We need to support 2 forms of invalidation-key: url and opensocial id.
Supporting invalidating url is relatively easy, cause key in cache is
RemoteContentRequest.
Supporting invalidating opensocial id means that we should invalidate all stuff
fetched by signed makeRequest related to a specified user. To support this, we
need to store these stuff into a new cachewhose key is user id and url.
4. If fetching failed, we can use cached version even if it's expired.
Because we need expired values to have higher availability, CacheApc and
CacheMemcache need to store time/ttl just like CacheFile. I refactored those
cache in 20090225.patch.
> add support for 0.9 limited invalidation
> ----------------------------------------
>
> Key: SHINDIG-943
> URL: https://issues.apache.org/jira/browse/SHINDIG-943
> Project: Shindig
> Issue Type: New Feature
> Components: PHP
> Reporter: Pan Jie
> Attachments: 20090225.patch
>
>
> http://wiki.opensocial.org/index.php?title=Limited_Invalidation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
