Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [RFC v1 1/1] doc/gatt-api: New API properties and methods for the GATT D-Bus API. From: Marcel Holtmann In-Reply-To: Date: Mon, 11 Aug 2014 12:03:33 -0700 Cc: "Gu, Chao Jie" , "linux-bluetooth@vger.kernel.org" Message-Id: <7BB5EFE5-886B-4422-AA58-99372B14380D@holtmann.org> 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> <3D02B219753AD44CBDDDE484323B1774112ECA19@SHSMSX104.ccr.corp.intel.com> To: Arman Uguray Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Arman, >> I have no major objections to the API, but just an API description is not enough. What is important to also deliver an implementation of this API. >> > > The implementation will come in the next few months as the shared > stack takes shape. The thing is, the existing proposal is not > accompanied by an implementation (it's not even included in the > release bundles) either and it looks like there are several parties > that are implementing their own version of the API based on the > unimplemented proposal. I think it makes sense to update it with the > changes that we discussed so that people can plan their code for > future compatibility. > > Either that or remove doc/gatt-api.txt entirely for the time being. then send me a patch that updates the API documentation for what it is suppose to be and deletes pieces are obsolete now. Regards Marcel