On Tue, Mar 3, 2009 at 4:43 AM, John Kemp <[email protected]> wrote: > > On Mar 2, 2009, at 5:37 PM, Brian Eaton wrote: > > > > > Ah, I totally forgot about the whole "consumer key" nomenclature. > > > > It would make me incredibly happy if OAuth talked about "consumer > > name" > > Exactly, the "consumer key" is an _identifier_ (a name) for the > consuming application.
Maybe consumer_id then ;-) Another thing which might be interesting would be to explain what all the parts are good for. Like why a consumer name/secret, why a request token and so on. I would assume that to some people it might not be directly clear and it probably helps implementations if people know more why they are doing things. But I haven't looked back into the spec so I am not sure if it's not maybe already in there. And (unrelated) another question: Is there a list of extensions somewhere? Would be good to prevent duplicating efforts. -- Christian -- Christian Scholz http://mrtopf.de/blog New Podcast: http://datawithoutborders.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
