On 13 May 2011, at 16:33, Ate Douma wrote: > On 05/13/2011 05:04 PM, Ate Douma wrote: >> On 05/11/2011 09:14 PM, Zhenhua (Gerald) Guo wrote: >>> There are two ways how Shindig SPIs are implemented. >> >> From a practical POV, I would expect using database access from Shiding for >> now >> should also be easier/quicker to implement (assuming the common database >> access >> logic is factored out in a separate module). >> And, as this database access layer is needed by the portal already anyway, >> there >> is little effort lost if we later on would decide to implement and leverage >> OpenSocial services from the portal instead. > > Another benefit I forgot to add of creating a separate database access module > would be that it allows creating other (portal independent) applications like > an admin console for maintenance purposes or reporting solutions which don't > need and possibly even are undesired to be integrated directly in the portal. > Of course, for that we could also add an additional REST or RPC services > layer within the portal (and we also can do both), but for low-level/admin > usage a direct database access layer probably might be easier and preferred. > >> >> Anyone else with an opinion or feedback?
A REST API does provide some flexibility. (Apache Wink is quite nice for generating a REST APIs.) >> >> Ate >> >>> >>> >>> Gerald >>> >>> On Tue, May 10, 2011 at 11:42 PM, Zhenhua (Gerald) Guo<[email protected]> >>> wrote: >>>> I just created a JIRA sub-task for OpenSocial Person related SPI >>>> implementation. >>>> The Person object is specified in OpenSocial spec 2.0 >>>> http://opensocial-resources.googlecode.com/svn/spec/2.0/Social-Data.xml#Person. >>>> In RAVE, we have already had User class. However, our existing User >>>> class serves different purposes than OpenSocial Person object. >>>> I am considering implementing Person related SPIs, at least GetPerson >>>> SPI, if nobody else is implementing it. In the first step, I will use >>>> our existing User class and expose basic user information (e.g. >>>> username) to Shindig. Then I will extend User class (or write a >>>> completely new class) to add more fields required by OpenSocial Person >>>> data structure/model. >>>> Any comments on this? Is the proposed implementation strategy appropriate? >>>> >>>> Thanks, >>>> Gerald >>>> >> >
