On Mon, Jun 15, 2009 at 3:00 PM, MannyNS <[email protected]> wrote:
> > Only if you had Kara Trace in your address book already. But if you > add it after you start monitoring, you need to query the whole > database to see if Kara has been added or not to your address book. I had assumed the person you are interested in would already be in your address book, otherwise how would you know that you want to play a sound when that person is removed from your contacts? And if she did, then you start monitoring of her. Imaging that you > have 10 different girls with name Kara Trace in your address book. How likely is that, really? Then you have to subscribe to 10 different URIs, and still to keep > monitoring if a new Kara Trace entry has been added to your address > book. Further, my application/service would have to subscribe to all > database changes, as someone may rename another contact and name her > Kara Trace. > Then, what if I want to add Sharon Valerii too? > The system will be overloaded with my observers, and the amount of > work is just... ridiculous. Yes, your examples would be a bit of work to implement. On the other hand, they seem a little far fetched, and not something you'd want to do in practice, so why don't you tell us what you're actually trying to accomplish, and maybe we can find a better solution? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
