Kevin,
That is what I am not able to understand. My question was how to make my
site's data (like user's friends and activity) available to the gadget. And
ur answer was this.

*"What do you mean by "pass my data"? What data are you referring to? Most
data about your container should be "passed" by implementing the open social
API according to your site's needs. You can get this data either by using
interframe communication (i.e. the "ifpc" feature), or by talking to some
back end with a security token. The security token scaffolding is mostly in
place now, but you'd still have to implement the back end and pass the token
your self."*

I can sense that this is what I want.  Can u explain this in simple words. I
know about ifpc (interframe procedure call). In the second option u say that
communication should be done with the backend with a security token. Can u
please explain that part in simple words? I didn't understand that. I know
this now... that a security token is issued to the gadget everytime the
gadget is rendered. Now what do I have to do to implement the communication
between my database and the opensocial gadget? I mean... my actual question
is this. Where do I tell the container or the gadget, that my backend can be
contacted like this?

On Feb 1, 2008 3:34 AM, Kevin Brown <[EMAIL PROTECTED]> wrote:

> On Feb 1, 2008 2:33 AM, Akash Xavier <[EMAIL PROTECTED]> wrote:
>
> > Kevin,
> > how do I pass my data to the gadget? I do make data available to the
> > gadget
> > when the makeRequest() is called?
> >
>
> What do you mean by "pass my data"? What data are you referring to? Most
> data about your container should be "passed" by implementing the open
> social
> API according to your site's needs. You can get this data either by using
> interframe communication (i.e. the "ifpc" feature), or by talking to some
> back end with a security token. The security token scaffolding is mostly
> in
> place now, but you'd still have to implement the back end and pass the
> token
> your self.
>



-- 
Akash Manohar
[EMAIL PROTECTED]

Reply via email to