I wouldn't suggest putting it in a Service unless it is really something you
want to have executing when the user is outside of your app.
For example, a browser typically wouldn't associate a Service with
networking, because all of its networking is there to serve the UI.
On Mon, Jul 18, 2011 at
Note that basically everything you do for dealing with a configuration
change is *exactly* the same thing you need to do to correctly handle your
app being killed in the background if the user has (temporarily) left its
UI. Thus making sure you deal correctly with a config change is a really
good
2 matches
Mail list logo
