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: <3D02B219753AD44CBDDDE484323B1774112ECA19@SHSMSX104.ccr.corp.intel.com> Date: Mon, 11 Aug 2014 10:49:06 -0700 Cc: Arman Uguray , "linux-bluetooth@vger.kernel.org" Message-Id: 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: "Gu, Chao Jie" Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Chaojie, the mailing list policy is to NOT top post. So please keep that in mind and do proper inline quoting. > 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 ? 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. Regards Marcel