On Sat, Jan 19, 2013 at 8:22 PM, dashman <[email protected]> wrote:
> I'm concerned about the overhead with this mechanism. > Why? > Also not too sure how to notify the service of a new job. > IntentService, as Kris mentioned, can just be called repeatedly and it will queue the messages up and handled them one by one. > If the foreground activity and service share an object - i assume i can > use standard java synchronization - i.e. wait() and notifyall() etc. > You shouldn't have to do that. What object would they be sharing? If they're running at the same time, then you probably want to bind to the Service which allows you to communicate with the Service directly. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
