iliketolearn wrote: > Otherwise, if I put > the service in the same process as the rest of my application, the > system would need to keep this massive process (containing various > views, activities, and a service) around continuously - something very > inefficient.
Only if you're holding onto references to all that stuff. Activities and their constituent views are designed to be closed up and reclaimed by the OS at will. That's part of the rationale for the whole Activity lifecycle and all its callbacks. Assuming you are allowing garbage collection to work (e.g., you are not holding onto an Activity in some static class variable or something), then I believe your process will not be much "heavier" than the service itself, because Android will reclaim all your activities and views when it needs to. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
