You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Glen Mazza <gm...@talend.com> on 2012/02/03 17:23:29 UTC
new Twitter component: switch from ConsumerKey/Secret to ClientKey/Secret?
Hi, the upcoming Twitter component
(http://camel.apache.org/twitter.html) has these two settings (among
others): OAuth consumerKey and consumerSecret. But "consumer" is a
deprecated term in the OAuth sphere:
http://tools.ietf.org/html/rfc5849#section-3.1 -- they're "clients"
today. Since 2.10 hasn't been released yet, should these parameters be
renamed to "clientKey" and "clientSecret" instead? If we're going to
change it, now is definitely the time...
Glen
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: new Twitter component: switch from ConsumerKey/Secret to ClientKey/Secret?
Posted by Glen Mazza <gm...@talend.com>.
OK, makes sense.
Glen
On 02/03/2012 11:30 AM, Brett Meyer wrote:
> Glen,
>
> I'd recommend not switching them for now. In Twitter's
> application/development areas, it still refers to the keys using
> "consumer" terms. Calling them "client" may be confusing when
> developer setup their apps in Twitter.
>
> Brett Meyer
> 3RiverDev.com
> brett@3riverdev.com
> 260-349-5732
>
>
> On 02/03/2012 11:23 AM, Glen Mazza wrote:
>> Hi, the upcoming Twitter component
>> (http://camel.apache.org/twitter.html) has these two settings (among
>> others): OAuth consumerKey and consumerSecret. But "consumer" is a
>> deprecated term in the OAuth sphere:
>> http://tools.ietf.org/html/rfc5849#section-3.1 -- they're "clients"
>> today. Since 2.10 hasn't been released yet, should these parameters
>> be renamed to "clientKey" and "clientSecret" instead? If we're going
>> to change it, now is definitely the time...
>>
>> Glen
>>
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: new Twitter component: switch from ConsumerKey/Secret to ClientKey/Secret?
Posted by Brett Meyer <br...@3riverdev.com>.
Glen,
I'd recommend not switching them for now. In Twitter's
application/development areas, it still refers to the keys using
"consumer" terms. Calling them "client" may be confusing when developer
setup their apps in Twitter.
Brett Meyer
3RiverDev.com
brett@3riverdev.com
260-349-5732
On 02/03/2012 11:23 AM, Glen Mazza wrote:
> Hi, the upcoming Twitter component
> (http://camel.apache.org/twitter.html) has these two settings (among
> others): OAuth consumerKey and consumerSecret. But "consumer" is a
> deprecated term in the OAuth sphere:
> http://tools.ietf.org/html/rfc5849#section-3.1 -- they're "clients"
> today. Since 2.10 hasn't been released yet, should these parameters
> be renamed to "clientKey" and "clientSecret" instead? If we're going
> to change it, now is definitely the time...
>
> Glen
>