Hi! I understood what you are trying to do, and yes, you should use REST and RPC. Activities is not a good example, since you just can post, not get the activities.
-Robson 2009/4/18 wolly <overl...@gmail.com> > > Hi, > > I am new to opensocial and I have a question relating to it. > > From the developer guide, it says the 3 main features of it are > * People and relationships. Members of social networks have > friends. OpenSocial applications use the connections between people > and their friends. > * Persistence. OpenSocial applications can take advantage of > persistence, the ability to store data that can be retrieved when the > application runs again at a later time. > * Activities. People use social applications to inform others > about what they're doing: going to a movie, posting photos, and so > on. > > If I want to extract e.g activities from 3 diff social networks and > consolidate into a central location, can I say that I should be using > these The OpenSocial REST and RPC protocols to get what I want? > > I m not looking to build an embedded Applications that use the > OpenSocial APIs within the social network. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to opensocial-api@googlegroups.com To unsubscribe from this group, send email to opensocial-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
