Re: [Exist-development] OAuth documentation

[Loren C. <lor...@gm...>]

I think that we also need the OAuth client for LinkedIn

On Oct 11, 2012, at 12:31 PM, Dmitriy Shabanov <sha...@gm...> wrote:

> On Thu, Oct 11, 2012 at 10:29 PM, Joe Wicentowski <jo...@gm...> wrote:
> Thanks, Dmitriy!  I'll work on that and may have some questions.
> 
> I will also contact you offlist about the possibility of adding
> twitter - which just disabled unauthenticated requests (and atom) -
> now the only way to get one's timeline is via OAuth-authenticated
> requests and JSON responses.  Ugh.
> 
> I see some demand for OAuth client, like twitter or gdocs needs.
>  
> 
> I'm suprised that we have to add support on the java level for each
> OAuth API provider - I guess they're not as standardized as they
> should be.
> 
> Yes, they are not -(
> 
> -- 
> Dmitriy Shabanov
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development