To add my 2 cents: - As my description [1] indicates, setting up the gadget server in anything else then Java is a lot of work at the moment. You'd have to port the entire java code to PHP, on the way solving alot of php specific issues. I would not recommend doing it until the Java Shindig server is "stable" (and you'll have a reference to program against). - The container in my description is PHP. I believe that the container and the gadget server need not be in the same language. At Hyves we'll probably go live with the container in PHP and Shindig in Java - I would suggest you to read, and follow the guide. I think it'll answer most of the questions you have. - To allow the container and gadget server to be language-independent from each other, I think the GadgetSigner implementation should be part of the Shindig specification (or Shindig Best Practices; not of the OpenSocial specification though). That would allow third parties to create GadgetSigners in all sorts of languages, that are compatible with (Java-)Shindig. Obviously, there is some need to share a secret, or share the link to a public key securly, between Container and Shindig Server. I'd like to see this specification sooner rather than later.
[1] http://trac.hyves-api.nl/hyves-api/wiki/ShindigStarted On 2/1/08, Akash Xavier <[EMAIL PROTECTED]> wrote: > > Kevin, > > I read Reinoud's blog entry. But it was about setting up a container in > java. > > On Feb 1, 2008 4:03 AM, Akash Xavier <[EMAIL PROTECTED]> wrote: > > > Kevin, > > > > This is what I am doing currently... > > I have all the javascript files of opensocial in a directory called > > 'osocial'. (only the javascript files of opensocial). And then I call > them > > after parsing and rendering the data. Thats what is my mindwork. > > > > Now whats that 'feature'? I have seen the features directory in Shindig > > svn. > > > > Ok Forget all this stuff we spoke about. > > Is there any doc that explains the method to create a container.... (a > > little specific to php)? > > > > > > On Feb 1, 2008 3:47 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > > > When you write your opensocial-0.[6|7] feature. > > > > > > On Feb 1, 2008 3:43 AM, Akash Xavier <[EMAIL PROTECTED]> wrote: > > > > > > > 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] > > > > > > > > > > > > > > > -- > > > > Akash Manohar > > [EMAIL PROTECTED] > > > > > > -- > Akash Manohar > [EMAIL PROTECTED] >
