Proposal for 0.8 - inline gadgets

[Martin Webb]

I can see a need for containers to support inline gadgets - as igoogle does.  But on a per case basis.  However the gadget server does not support inline gadgets - even whitelisted ones.

--
Internet Related Technologies - http://www.irt.org

[John Hjelmstad]

I think this is already achievable with the existing spec.

Any given server implementation - Shindig's, for instance - is free to respond to a given query with unmodified gadget content as it wishes, eg. in its metadata API responses. I strongly suspect that any given container integrating gadgets will inline only whitelisted content. Modifications could be made to their gadget rendering server making this happen, and the existing __MODULE_ID__ substitution facilitates functionality of these gadgets when inlined.

Thoughts?

Best,
John

[Gary Helmling]

I'm currently doing this with my own (admittedly limited) container
setup (still in development) based on Shindig. So I agree, I don't
see any spec changes needed to support this at the moment... But I'm
still mid-process so maybe I'm missing something?

FYI, yep, I only inline my own whitelisted gadgets, inlining untrusted
third-party content would be bad. And some structural changes to the
Shindig code might make this a little easier to do, but I'll be
bringing that up on the Shindig dev list.

--gh

[Cassie]

To confirm: not including this as part of 0.8 as it does not require any spec changes. Containers are free to do what they like.