Very interesting idea. Actually I've personally put some efforts on this idea. Some challenges I've faced includes:
1. Latency. Since these 2 containers might not locate in the same data center (in most of the cases), the data fetching latency could be a serious issue. 2. Security. There need to be some kind of secure tunnel between the 2 containers, plus ip-whitelist filtering. 3. Authentication. Given the data request flow is Client -> container1 -> container2, it introduces two authentications. Unless there's a tight business deal signed by container1 and container2 that they trust each other, it will be difficult for the client to push the authentication credential (for container2) through Client -> container1 step. 4. Incentive. If container2 already has a Shindig installed, they may have much less incentive to connect it to another container (as front-end). Just my $0.02. Hopes they helps. Regards, Jacky On Thu, Mar 11, 2010 at 6:04 AM, Niels van Dijk <[email protected]> wrote: > Hi, > > Has anyone every tried to introduce a persistent data layer in a > container based on another OpenSocial containers content? > This could be done by implementing a php or java OpenSocial client in > the persistent data layer to consume a remote container's rest api. > It would for example be interesting for combining a local set of users > and groups with a remote set, or to create a 'mashup' of 2 remote > containers. > If anyone has any experience with this I would love to hear what was > done to make this work. > > thanx! > Niels > > -- Best Regards, Jacky Wang (Office) +86-10-6250-3316 (Mobile) +86-1381-0018-677 Kejian Building, Tsinghua Science Park Building 6 No.1 Zhongguancun East Road, Haidian District Beijing P.R.China 100084
