Keith Grennan wrote: > Howdy, > > In the last couple months all the questions I've been asked about > Net::OAuth (OAuth for Perl) have been around creating 2-legged / > tokenless requests. > > I know this is not the primary OAuth use case, but it may be > worthwhile for other OAuth library maintainers to include support (and > docs, unit tests) for the 2-legged scenario, if they haven't already. > > >
Oddly, I think it may become one. (and possibly we're to blame) Netflix uses two legged OAuth for general requests like getting catalog information. For us, OAuth provides a way to ensure that a developer's ID isn't compromised. Three legged OAuth is only used where there's a potential third party involved (e.g. access to a Netflix User's movie rental queue or other more private information.) I know a number of groups are thinking along the same path because of the issues and headaches that come with managing things like AppIds. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
