OK, I need my service to continuously run in the background and not be bound to the life cycle of the main application. The service needs to keep data in an ongoing notification up to date. I have this working fine and the two communicate via Messages over registered Handlers (handler registration done in main app's bind/unbind).
Now I need my service to send and receive an HTTP request at some interval and I don't want it to block waiting for the request (it may need to accept Messages from the main app during this time). So I am using an AsyncTask which sends the request and receives it (in doInBackground), and then puts the data in a Bundle and sends it on the Messenger (in onPostExecute) and uses the data to update the ongoing notification. So yes, I am using AsyncTask for background data retrieval and processing. I am also using an Service which starts at boot time, refreshes the data hourly, and keeps the ongoing notification alive. I verify that this Service is running/updating every hour via AlarmManager. I suppose that I should put the data into a ContentProvider every hour. But I still need the Service to keep the ongoing notification active and updated. I'm not sure that any of this will help at all with the debugger hitting breakpoints in my AsyncTask though. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
