Re: Best practices for using GOA

[Debarshi Ray <rishi is lostca se>]

On Thu, Jun 28, 2018 at 01:08:10PM +0200, Bastien Nocera wrote:
> It was done this way because the GOA API is just a small shim on top of
> the ObjectManager API. Ideally, you would block those signal emissions
> if they were synthesised because of the daemon disappearing.
>
> The ObjectManager API isn't so great when you have data on the client
> side. We also use this API for BlueZ/gnome-bluetooth, and there's no
> storage on the gnome-bluetooth side, so an "object-removed" translates
> to hiding the device, whether or not the daemon is running. We would
> need to add a similar technique to the one you should use in GOA if we
> did have something stored on the gnome-bluetooth side though.

Ok. Thanks for the context!