Doug as I said to Jiho, I did not see any support out of the box for these. You may be able to use some of the container lifecycle events in order to know when to call the lifecycle events defined in the gadget. For example the containers unload event could be used to know when to call the REST endpoint for the event.removeapp.
-Ryan From: daviesd <[email protected]> To: shindig <[email protected]>, Date: 03/28/2012 03:23 PM Subject: Gadget Lifecyle Event vs. Container Lifecyle Events I know there is discussion about this topic over on the OpenSocial and Gadgets Specification google group. So please let me know if I¹m polluting this maillist with something that shouldn¹t be discussed here. I¹ve been pretty familiar with the container lifecycle events available via addGadgetLifecycleCallback and have plugged into some of them (onNavigated). Until recently I didn¹t even know about the gadget lifecycle events ( http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#Li feCycleEvents ). First off does shindig even support these? (I think Jiho Hwang just asked a similar question -- http://markmail.org/message/3zk3pr2dabkf7pem). Next, it seems like this is really for gadget developers to provide restful callbacks so that they can track their own apps and not for me as a container developer to track anything. However, I have the need as a container developer to start tracking some of these events. For example a gadget has been installed/uninstalled (whatever that means). Should I just being doing this from within each of my specialized container functions (where I actually install an app and use our spaces implementation) or is there a similar container callback approach that I can plug into? I hope that makes sense. Thanks, Doug
