Gadget lifecycle registry for the container

[Igor Belakovskiy]

We added some enhancements to the container spec to allow features to
register callbacks for gadget lifecycle events.

Patch and description available here:
http://code.google.com/p/opensocial-resources/issues/detail?id=1185

Any comments are welcome.

Thanks,
-Igor

[Matthew Marum]

I've applied the spec patch.

[rbaxter85]

Thanks Igor and Matt.

[Matthew Marum]

We should make sure that this proposal and the web hook based lifecycle events are aligned where possible.

http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#LifeCycleEvents

I've updated the Core-Gadget spec language around Gadget Lifecycle events to accommodate the existence of other possible event mechanisms.

[rbaxter85]

Matt I think we briefly talked about this on Tuesday. There is some
confusion between the events Igor proposed, and these "Gadget
Lifecycle Events" which already existed in the core gadget spec.
Igor's lifecycle events are for notifications of the gadgets lifecycle
in the container. Consumers of these events are generally other
features in the container which need to know when certain gadgets are
preloaded, loaded, closed, and unloaded from the container. The
lifecycle events in the core gadget spec are targeting the gadget
developer. I agree there are some similarities, but the use cases are
totally different. We need to add to change the name of one of these
so we can distinguish the two.

On Jul 14, 9:20 am, Matthew Marum <mgma...@gmail.com> wrote:
> We should make sure that this proposal and the web hook based lifecycle
> events are aligned where possible.
>

> http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.x...

[Matthew Marum]

I totally agree we are looking at different use cases when considering the Container events and the web based events.

I think of the Gadget Lifecycle as a single thing (Gadget gets installed, used, removed, etc.) where we've defined 2 different ways to receive events about that lifecycle.  One way uses the web hooks via the Link element in the gadget specification.  The other way is by registering a listener with the Container so we can get events within the browser.

Lets talk about this tomorrow during the OpenSocial 2.0 call at 10am EST.