Hi, Louis,
I am a little confused by limited invalidation in java shindig. Here are my
questions.
There are 3 entries for limited invalidation in opensocial spec 0.9:
1. json rpc
Example from spec:
POST /api/rpc
HOST opensocial.example.org
Content-Type application/json
{
method : "cache.invalidate",
params : {
invalidationKeys : [ "example.org:12345", "example.org:4567",
"3456778", "http://www.myapp.com/gadgetpec.xml";]
}
}
Differ from social rpc request, whose entry is "/social/rpc", entry for
cache invalidation request should be "/gadgets/rpc", right?
It works when using "/gadgets/rpc" as path in my local instance.
For singed request, oauth parameters should be placed in headers, and post
body should be hashed in oauth_body_hash, right?
Example:
POST /gadgets/rpc
HOST opensocial.example.org
Authorization: OAuth [oauth_nonce=xxx, oauth_timestamp=xxx,
oauth_body_hash=xxx, ..., oauth_signature=xxx]
Content-Type application/json
...
Are there anything wrong with http headers for my example?
2. restful api
Example from spec:
Invalidate the gadget spec and message bundle of an application using REST
POST /api/rest/cache/invalidate
HOST opensocial.example.org
Content-Type application/json
{
invalidationKeys : [ "http://www.myapp.com/gadgetspec.xml";,
"http://www.myapp.com/messagebundle.xml";]
}
I tried "/gadgets/rest/cache/invalidate" and I received a 404 response. I
also checked servlet-mapping and didn't find anything related to url-pattern
"/gadgets/rest". Am I missing anything?
3. javascript api
>From opensocial spec 0.9:
5.3.1.2.3<file:///C:/wamp/www/opensocial-resources/spec/0.9/OpenSocial-Specification.xml#rfc.section.5.3.1.2.3>
invalidateCache<file:///C:/wamp/www/opensocial-resources/spec/0.9/OpenSocial-Specification.xml#opensocial.invalidateCache>
<static> opensocial.invalidateCache()
Description: Invalidates all resources cached for the current viewer.
But I couldn't find implementations for invalidateCache.
--
Warm Regards,
Pan Jie
[email protected]
