On 5/13/11 11:33 AM, "Ate Douma" <[email protected]> wrote: >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.
This sounds similar to the approach that Jesse took internally for OSEC (unless I am misreading the comments). He created a backend person REST service that both Shindig and OSEC connect to. Given that Rave is going to be integrating multiple widget renderers, it might make sense to build a central component that manages the data store for information (like person) that is common amongst all components, then provide an API for access by Shindig, portal and Wookie. >
