Reviewers: dev_shindig.apache.org,
Description:
Implementation of the Albums MediaItems services within Apache
Shindig. Includes the handlers, services, and sample JSON DB
implementation.
Please review this at http://codereview.appspot.com/1961047/
Affected files:
There is also a patch on jira that fixes this problem,
you can apply it to test oAuth (but maybe do not use it for production,
since the patch was not committed to shindig)
https://issues.apache.org/jira/browse/SHINDIG-1334
E.
On 25/8/10 10:48, Paul Lindner wrote:
yes, you'll need to escape
I'm trying to clarify if appData is supposed to be shared or distinct across
multiple instances of the same gadget(appId) for a given user (per the
opensocial standard).
I have initially implemented appData and userPrefs as dinstinct per instance.
Now I'm reading this wiki example and
Thanks Paul, Twitter implements OAuth2?! If no, why would LinkedIn Tweets
App expect OAuth 2 support in proxy?
I see your changes to UrlParameterAuthenticationHandler for the reverse
situation, hopefully v2 draft's rev 10 stays, Facebook for instance doesn't
use oauth_token but access_token as
The way we've implemented it in our system is to have appData indexed
by (user, appId) and for userPrefs to be per-instance. So the
behaviour you describe, where appData is shared between two copies of
the app on their profile, is exactly how we've done it.
I must admit, though, that I can't for
