What is the simplest, correct way to implement an application with background semantics similar to the media player? To the user it should appear as an activity which can be kept running in the background and "iconized" to the notification bar whenever the activity is not on top of the stack or until stopped explicitly.
I guess some of the choices would be: a) An activity which ignores onPause/onStop and just keeps doing whatever it is doing (simple, but I suspect not the recommended way...) b) Activity + in-process service c) Activity + service with its own process Assuming the solution involves a service, what are the choices for sharing a fair amount of state between the activity and its service? Can they just access shared objects (how to set that up) or does it require an AIDL RPC interface storing everything in a database instead? Bernhard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
