Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1405986034-29122-1-git-send-email-armansito@chromium.org> <1405986034-29122-2-git-send-email-armansito@chromium.org> <3D02B219753AD44CBDDDE484323B1774112D2C2C@SHSMSX104.ccr.corp.intel.com> <409335B4-82B3-40D2-970A-D39416F02591@holtmann.org> <3D02B219753AD44CBDDDE484323B1774112D2F48@SHSMSX104.ccr.corp.intel.com> Date: Thu, 31 Jul 2014 20:11:23 -0700 Message-ID: Subject: Re: [RFC v1 1/1] doc/gatt-api: New API properties and methods for the GATT D-Bus API. From: Arman Uguray To: Marcel Holtmann Cc: "Gu, Chao Jie" , "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: 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.