[OpenSocial] Re: integrate Server side code - Balaji Srinivasan - com.googlegroups.opensocial-api

21 messages in com.googlegroups.opensocial-api[OpenSocial] Re: integrate Server sid...

From	Sent On	Attachments
afaq	15 May 2008 00:27
Shubhajyoti Ghosh	15 May 2008 03:18
rana das	15 May 2008 03:27
afaq	15 May 2008 03:44
afaq	15 May 2008 04:05
justin kruger	15 May 2008 05:16
afaq	15 May 2008 06:38
Renato Mangini	15 May 2008 06:52
Arne Roomann-Kurrik	15 May 2008 09:59
Arne Roomann-Kurrik	15 May 2008 09:59
justin kruger	15 May 2008 10:38
Balaji Srinivasan	15 May 2008 10:46
Balaji Srinivasan	15 May 2008 10:48
Balaji Srinivasan	15 May 2008 10:49
Balaji Srinivasan	15 May 2008 10:49
Renato Mangini	15 May 2008 10:54
Balaji Srinivasan	15 May 2008 11:45
Balaji Srinivasan	15 May 2008 11:45
Shubhajyoti Ghosh	15 May 2008 23:15
Renato Mangini	16 May 2008 06:24
buzypi	22 May 2008 12:02

Subject:	[OpenSocial] Re: integrate Server side code
From:	Balaji Srinivasan (bala...@gmail.com)
Date:	05/15/2008 11:45:03 AM
List:	com.googlegroups.opensocial-api

I didnt mean to imply that a client library was essential...just that its a convinience. See the Google Calendar API. Using the pHP client is obviously far easier than trying to write your own code. Ofcourse if the language is not supported, one could write to the spec.

Balaji

On May 15, 2008, at 10:54 AM, Renato Mangini wrote:

a REST API doesn't need a client lib. All you need is to be able to make HTTP requests, which all languages are capable of. The REST API would allow your outside code to communicate to a opensocial container. The makeRequest javascript call, which the iRead app uses, allows a gadget running inside a opensocial container to communicate to your outside code.

The difference is essentialy who starts the connection (and of course, the REST API would be limited to what is exposed, while the makeRequest is able to send any information a gadget is allowed to see).

On 5/15/08, Balaji Srinivasan <bala...@gmail.com> wrote:

Wouldnt this be done using the REST APIs? I assume we will have client libraries for the REST APIs in the language of your choice. (My choice would be PHP :)

On May 15, 2008, at 10:38 AM, justin kruger wrote:

maybe you want to start a project on google code to make open social more accessible to asp devs?

On Thu, May 15, 2008 at 11:59 AM, Arne Roomann-Kurrik <api....@google.com> wrote:

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 <mang...@gmail.com> 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 <Afaq...@gmail.com> 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

"If you are successful, it is because somewhere, sometime, someone gave you a life or an idea that started you in the right direction. Remember also that you are indebted to life until you help some less fortunate person, just as you were helped." --Melinda Gates