Hi marcel, For the New Gatt DBus API definition is important for user to use, so through the discussion, arman's proposal make much sense. Will this proposal be accepted and when wiil bluez announces new Gatt API ? Thanks Chaojie > -----Original Message----- > From: linux-bluetooth-owner@xxxxxxxxxxxxxxx > [mailto:linux-bluetooth-owner@xxxxxxxxxxxxxxx] On Behalf Of Arman Uguray > Sent: Friday, August 01, 2014 11:11 AM > To: Marcel Holtmann > Cc: Gu, Chao Jie; linux-bluetooth@xxxxxxxxxxxxxxx > Subject: Re: [RFC v1 1/1] doc/gatt-api: New API properties and methods for the > GATT D-Bus API. > > Hi Marcel, > > I think this all makes sense and the API is in a reasonable shape now. > All of the properties/methods can integrate nicely with client and server > implementations (with one or two properties being optional for server). I think > we can revisit GattManager1 once we start thinking about the server code but > for now I think this is good for client. > And, of course, we can always add new properties/methods later. > -- > 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 ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
