Hi Chaojie, > Following your new proposal to implement, there is one details that I missed before which condition the services would set up under the local remote device. I think this "optional" maybe is not essential. Gatt Hiearchy should always set up when it connected to remote devices. > I marked it as optional since it only applies when BlueZ is the central. If BlueZ is acting as a server for services that are registered through GattManager1, then this property doesn't make much sense. Even though the server-side implementation won't happen for some time, the idea is that server and client D-Bus APIs will use the same interface definitions. Thanks, Arman -- 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
