The data observer lifespan isn't tied to the receiver, it's a static. Also note that collection based widgets use other components, such as the remote views factory, and the service which acts as a factory for said factory (!).
This service is implemented by the framework as sticky, what you call the eternal service anti-pattern, and certainly affects the process' lifecycle. I believe there is also content provider in there somewhere. 17.05.2012 18:26 пользователь "Mark Murphy" <[email protected]> написал: -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
