If you want to use standard OAuth libraries, use a full set of
credentials: consumer key and consumer secret, token and token
secret. It's more than you need, but some libraries require it all.
If you need help using a specific library, this is a pretty good place
to ask.
On Apr 14, 10:32 pm, p
It's also similar to the way Amazon S3 URIs work, except with S3 the
timestamp is actually the expiration date for the URI (as opposed to the
time that the request was created) and there's no nonce (URIs can be used
repeatedly until they expire). You may want to take a look at their API for
some mo
Pretty sure this is what Digg is ostensibly doing.
Maybe Joe Stump can shed some light.
Chris
On Wed, Apr 15, 2009 at 11:19 AM, pkeane wrote:
>
> Great -- just what I was hoping to hear. I didn't want to start
> implementing if there was a known deal-breaker that I was not seeing.
> The caveat
Great -- just what I was hoping to hear. I didn't want to start
implementing if there was a known deal-breaker that I was not seeing.
The caveats you mention, while important, are not deal breakers give
what we need.
--peter
On Apr 15, 12:48 am, Mike Malone wrote:
> Yea, that would work, some
Yea, that would work, some caveats apply though.
First, it sounds like you may not need all of OAuth, but if you want to take
advantage of the existing libraries and whatnot the extra OAuth features
probably won't cause any problems.
As you said, you'll want to generate signed OAuth URIs for the
