Hi Adam, > Hi Luiz, > > You are right - though I still like the initial design of having one > service per ObjectManager, as it makes it easier to cleanup or restart (or > D-Bus export/unexport) an individual service at the ObjectManager API > level. > > I only added the pointer to manager_path because it was better to test > that for that prefix than it was to not do any checking. I couldn¹t do > the stronger test for the GattService path because there is no guaranteed > order to the proxy callbacks. Please check the patch-set Ive sent last week, the idea is that you would register the application only once, later on we might implement support for InterfacesAdded/InterfacesRemoved allowing services to be added/removed without having to unregistering and registering again. > How strict do you think we need to be here in validating the parent/child > relationships in the object tree? Right now it expects the objects to appear in order, service -> characteristic -> descriptor, so that we can established proper relationship between the objects. I did not add any check for multiple applications within the same connection id except if it is the very same object path given for the object manager. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
