Yea i'm getting the feeling it should've been something like that,
thanks :)
-- Chris
On Jul 2, 2008, at 1:25 AM, Brian Eaton wrote:
Any possibility the gadgets are adding this themselves?
On Tue, Jul 1, 2008 at 4:15 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
Anyone have any idea about this btw?
The question is 'how does a gadget developer know what syndicator/
container
this is?'
In a rush to get iLike and rockyou apps ready for demonstration @
the google
io we added some hard coded params to the signed makeRequest, there's
already:
- oauth_nonce
- oauth_timestamp
- oauth_consumer_key
- oauth_token
and we added synd/container to this, at the request of the gadget
developers. However looking at the Java code now, we don't see those
synd/container params in the oauth request, so hence the question
above
Maybe we're on a wrong trail here and we missed something
completely obvious
though :)
-- Chris
On Jul 1, 2008, at 8:29 PM, Gonzalo Aune wrote:
Yes, youre right, but in apps like iLike you need to pass extra
parameters
like 'container' and 'synd', we mannually added those params in
PHP, but i
cant find where Java does this.
G.-
On Tue, Jul 1, 2008 at 2:21 PM, Brian Eaton <[EMAIL PROTECTED]>
wrote:
On Tue, Jul 1, 2008 at 6:21 AM, Gonzalo Aune
<[EMAIL PROTECTED]>
wrote:
i've been looking to fix a bug in the PHP Shindig OAuth module,
and i
found
that we have to put into the request the synd and container
params (ie,
to
get things work in iLike or Hi5), i was trying to look at the
Java code,
but
i didnt find any tip on how Java does that, Java only appends the
xoauth_app_url param, but nothing more, can anybody tell me if
we really
need this or maybe there is a way to avoid passing that
variables to the
container?, Thanks in advance.
The oauth.net java code (which Shindig for Java relies on) adds the
consumer key parameter. You really do need it, otherwise the
recipient has no idea who sent the message or what key they
should use
to verify the message.
