So if I need to monitor N different services, I'll need to repeat the requests N different times, and set up N different signal connections to watch for changes? That seems a bit overboard when the D-Bus interface was designed so this could be handled in one go.
I agree that a change like this needs to be tested with existing users of the API. Do you have a list of such users so we can find out whether it actually causes a problem? I'm kind of curious, since any application that receives multiple service IDs from the D-Bus daemon is almost certainly seeing unpredictable behaviour from the current version of the client library. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602159 Title: Manager class only provides access to one (random?) service ID for an account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/online-accounts-api/+bug/1602159/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
