Renato's description is very accurate from what I see. The iRead gadget uses signed makeRequest calls to transmit data about the gadget owner/viewer back to their site for the purposes of interacting with their account. The rest of the data is pulled from their JSON API.
~Arne On Thu, May 15, 2008 at 6:52 AM, Renato Mangini <[EMAIL PROTECTED]> wrote: > > Afaq, > > As I could see on iRead's site, there is no server side active opensocial > component. The opensocial features only works actively inside a opensocial > container. Probably (my assumption), the opensocial gadget talks back to its > server, sending the information required to its application. If that's the > case, the only opensocial-related code on the server should be the > authentication and verification of container's encryption key, to avoid > being spoofed. In other words, the server could be the plain old web > services we all know about. > > > -- > Renato Mangini > http://www.linkedin.com/in/mangini > > On 5/15/08, afaq <[EMAIL PROTECTED]> wrote: >> >> >> hi, >> >> >> > aspx is not designed to produce gadgets. it may be easier to render >> > the gadget XML in some other way using c# or vb.net. >> >> >> That is true.But i am still not satisfied with this reply. i have seen >> web site like >> http://booksiread.org/ where server side is integrated open social. >> There must be some >> integration tip / trick for server side. >> >> Can anybody from group provide directions. >> >> looking to hear. >> >> regards, >> >> Afaq >> >> > > > > > -- OpenSocial IRC - irc://irc.freenode.net/opensocial --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
