That's currently not possible, because you cannot reach a opensocial 0.7
container from outside-in, only the opposite way (inside-out, i.e., a gadget
running inside the container contacting your server).
That's the purpose of the REST API, which may be released on the next
version.
On 5/16/08, Shubhajyoti Ghosh <[EMAIL PROTECTED]> wrote:
>
>
> What i'm looking for is to build a C# component that i can reference
> in my projects. I would add the component as a reference to whatever
> app i'm building. The C# component for now, could have a single
> method.
>
> Here is a suggested method signature.
>
> GetContacts(string socialnetworkname, string username, string
> password)
> {
> implement code;
> }
>
> Inside this method, you would use the "socialnetworkname" to determine
> which social network site to connect to. you would then user the
> "username/password" to authenticate with that service using the
> OpenSocial Javascrpt API, and then you would call the appropriate
> method to return that persons contacts from that site. The return
> object would have a list of "people" objects, with properties for
> first name, last name, email, etc, etc...as much info as I could
> retrieve using the javascript api.
>
> Welcome Suggestion
>
>
> On May 15, 11:45 pm, Balaji Srinivasan <[EMAIL PROTECTED]> wrote:
> > 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 <[EMAIL PROTECTED]> 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 :)
> >
> > > Balaji
> >
> > > 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
>
> > > > <[EMAIL PROTECTED]> 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 <[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
> >
> > > > --
> > > > --
> > > > Justin Kruger
> > > >http://jDavid.net
>
> > > > [EMAIL PROTECTED]
>
> >
> > > > "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
> >
>
--
Renato Mangini
http://www.linkedin.com/in/mangini
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
