Use the "work queue processor" pattern inherently present in IntentService 
where all the request are serialized into a FIFO queue. Let the refresh 
logic and the content provider send intents to the service with distinct 
actions and you can be sure that they won't be fighting with each other.

-- 
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

Reply via email to