Looks good for me too +1.
On Fri, Jun 22, 2012 at 10:40 AM, Henry Saputra wrote:
> Used the generated jars to test in the container application and run
> basic gadget flow (no OAuth and crypt codec flows though)
> REST and OSAPI calls looks good.
>
> Signature looks ok (only check for common, ga
Used the generated jars to test in the container application and run
basic gadget flow (no OAuth and crypt codec flows though)
REST and OSAPI calls looks good.
Signature looks ok (only check for common, gadgets, social-api, and
feature modules)
+1
- Henry
On Mon, Jun 18, 2012 at 6:54 PM, Ryan
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5420/#review8482
---
The CodeAuthorizationResponseHandler picks up the gadgetUri from the a
Doug,
It's not something I plan on doing (the customers I support that are using
OAuth2 have all written their own client admin features which wouldn't make
sense outside of shindig.)
I understand - at a high level - what you want and why you want it. I'm
afraid I would steer you wrong on adding
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5420/
---
(Updated June 22, 2012, 11:18 a.m.)
Review request for shindig, Stanton Sievers
