Are you trying to tell me that it's totally safe to throw stuff in static fields? I've always avoided it because of years of shared space in a JVM in web apps. I know Android uses separate processes for each application but is it safe to say that it will kill all of your static allocations even if you don't clean them up properly?
If that's the case, then yes, I probably could have gotten away with using a static gateway instead of a remote service. On May 29, 12:18 pm, Mike Hearn <[email protected]> wrote: > > I DO need it to run in the background, that is, while orientation is > > changing. > > That's not "in the background" - the activity manager will keep your > process alive during configuration changes anyway, regardless of > whether you have a service or not. The only reason to use a service is > if you need your process to live on when the activities are not on > screen. > > > I don't like the static handler idea > > because it can't have more advanced capabilities like the queue my > > service has. > > Sorry, I don't understand this. You can pass any objects you like > through a handler and handlers use the threads message queue anyway. > So I don't see why you can't have a queue using a handler. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
