But why are sites like MySpace, Xing etc. already experimenting with
the SPI side? It seems Google has favored some social networks while
the rest is waiting for documentation. We have had great success with
other APIs with limited documentation and I bet most people in this
group could pull it off. As a group we could get this working without
too much assistance, so Google, please point us to a place where we
can access the same SPI software/documents as the other social
networks that are currently experimenting with it.

Arean.

On Nov 6, 8:26 am, Arean <[EMAIL PROTECTED]> wrote:
> Thank you. I will look into the gadgets first.
>
> On Nov 5, 7:09 pm, murtada <[EMAIL PROTECTED]> wrote:
>
> > Hi Arean,
>
> > I have reviewed the opensocial API extensively, as well as read most
> > all of the documentation. Your best bet would probably be to begin
> > supporting google gadgets on your website. While that is being
> > implemented, hopefully more details of the SPI can be found.
>
> > Murtada Shah
> > Serene Technologieshttp://serenetechnologies.ca
>
> > On Nov 5, 4:37 pm, Arean <[EMAIL PROTECTED]> wrote:
>
> > > hi,
>
> > > After reading the current information on this API it is not clear to
> > > me what exactly we need to open up our site to gadgets/apps to have
> > > access to our members' connections and activity. The People API
> > > references ATOM and REST  but mostly from the application developer's
> > > point of view.
>
> > > Where do we find the setup and development documentation to prepare
> > > our server and software to support this API?
>
> > > Arean.
> > > Konnects Inc.www.konnects.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Container Developers" 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-container?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to