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 Twitte
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
br...@3riverdev.com
260-349-5732
On
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.1
Hi Raul,
I had a look and the mongodb component, it looks ready, great job.
Few notes:
I think the unit test should not depend on existing mongodb
installation, it would be great if there is an inmemory or mock
implementation and the tests start it up for example.
Minor, you can make MongoDbCons
