implement parts of the the OpenSocial REST-API

[Robert Jäschke]

Using Apache-Shindig, we need to implement (at least!) the Interfaces

org.apache.shindig.social.opensocial.oauth.OAuthDataStore org.apache.shindig.social.opensocial.spi.ActivityService org.apache.shindig.social.opensocial.spi.AppDataService org.apache.shindig.social.opensocial.spi.MessageService org.apache.shindig.social.opensocial.spi.PersonService

(see http://shindig.apache.org/shindig-1.1.x/apidocs/index.html)

To discuss: * What will be our consumerId (the plain user name? there are user names incompatible with the OpenSocial spec!) * How will we represent our publication data?

[Robert Jäschke]

Hi Folke,

Da gibt's schon einen Eintrag für. Oder bekäme den Stephan?

[Lena Hettinger]

Maximilian is updating Shindig to version 2.5 for another issue. One question would be if all of these interfaces are still implemented in version 2.5 as Maximilian has already discovered that some classes from version 2.0 are now missing.

[Robert Jäschke]

In our last phone conference we settled the decision to remove OpenSocial support from the REST API since it is not used. Thus, I think rather than implementing those interfaces, the task is to remove or at least disable code for OpenSocial.