On Thu, Feb 21, 2013 at 8:41 PM, Gonzalo Aguilar Delgado <[email protected]> wrote: > Hello Chris, > > Ok. I see. > > So it's at least a little overlapping in the two providers, since both > provide rendering service. > > I'm a little lost about OpenSocial because for me it's Wookie + Social > API all together.
OpenSocial's rendering model is a little different from Wookie/W3C. Same goes for some of the convenience API, service definitions and runtime environments. > > Thank you. > > > El jue, 21-02-2013 a las 17:34 -0700, Chris Geer escribió: > >> On Thu, Feb 21, 2013 at 5:13 PM, Gonzalo Aguilar Delgado < >> [email protected]> wrote: >> >> > Hello, >> > >> > I deployed the application using a custom project. Just to have an idea >> > of what's the minimun required to run the frontend. >> > >> > I found that the application does not run after login because it's >> > waiting for >> > >> > localhost:8080/rpc >> > >> > This address is cleary provided by the ROOT context that seems to >> > contain Shindig. >> > >> > >> > Why is Shindig needed? >> > >> >> Rave requires that there is at least one provider. You have a choice right >> now between Wookie (W3C) or Shindig (OpenSocial). I believe that all the >> sample gadgets deployed out of the box are OpenSocial gadgets so Shindig is >> required. >> >> >> > It seems to run well without wookie. At least after login in with >> > "canonical". >> > >> > What does Shindig provides? Because I suppose that should only be needed >> > for the OpenSocial api, but does it provides anything else? >> > >> >> Shindig provides everything for OpenSocial including gadget rendering. >> >> > >> > >> > Thank you a lot in advance. >> >
