Just use a queue to feed the IntentService (or have a queue in it). On Wednesday, July 17, 2013 12:51:57 PM UTC+3, fr1550n wrote: > > My app uses a SyncAdapter to periodically sync server data to SQLite. It > also syncs in response to a GCM message that indicates new/updated server > data; via.an IntentService. > > These components each do their work in different background threads and > are created by different system processes (SyncManager/GCM broadcast) and > have different lifecycles. > > I'm requesting ideas on how best to fault-tolerantly co-ordinate/control > these components, e.g for an configuration Activity to signal to both that > they should do no work; e.g: to signal to the SyncAdapter to do no work > when the GCM IntentService is working. > > Abandoned ideas: StickyBroadcasts seem like overkill, SyncStatusObserveris > too simple. I'm not sure how to obtain my extended Application instance > in the SyncAdapter else I'd try and use that. > > Thanks > >
-- -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.