Hi, this is my first post to the group, so I would like to say first Android is great. I was surprised by how easy it is to develop applications based on this technology.
My questions are related to the two ways of managing service, started and bound. 1. I think that our application functionality requires both started/ bound. One thing is that the service will be responsible for running rather long operation, and the other is that we want to be able to access service from any activity at any point in time in order to get some complex data. Are there any "design" objections against implementing both approaches in the same service code? Is there a more suitable / recommended way to do this? 2. If the service is implementing both approaches, will there be only a single instance of a service handling both start/bound requests? I would like to avoid case when "start" launches one instance of a service, and following bound is connecting to another instance. I think there will be only single instance, just want to be sure. If documentation clarifies this somewhere, I would greatly appreciate a link. Regards, Bartek -- 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
