t;-Original Message-
> >From: daviesd [mailto:davi...@oclc.org]
> >Sent: Tuesday, November 22, 2011 10:01 AM
> >To: dev@shindig.apache.org
> >Subject: Re: Oauth 2 consumer implementation
> >
> >So how does a gadget know what service name to use since every
>-Original Message-
>From: daviesd [mailto:davi...@oclc.org]
>Sent: Tuesday, November 22, 2011 10:01 AM
>To: dev@shindig.apache.org
>Subject: Re: Oauth 2 consumer implementation
>
>So how does a gadget know what service name to use since every container
>could def
pers to register the provider
> information, but this is outside the scope of Shindig and the OpenSocial
> spec.
>
> -Ryan
>
> Email: rjbax...@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile
>
>
>
> From: Michael Matthews
> To: ,
> Date
Profile
From: Michael Matthews
To: ,
Date: 11/21/2011 02:27 PM
Subject:Oauth 2 consumer implementation
My organization is investigating implementing a "production-ready" version
of Shindig's OAuth2 Consumer implementation. After reviewing the wiki at
ope
My organization is investigating implementing a "production-ready" version
of Shindig's OAuth2 Consumer implementation. After reviewing the wiki at
opensocial.org (in particular
http://docs.opensocial.org/display/OSD/OAuth+2.0+Consumer+Implementation+in+
Apache+Shindig) and studying the code to Sh
