Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1322129290-10767-1-git-send-email-sancane@gmail.com> <20111202112957.GC17203@x220.ger.corp.intel.com> Date: Fri, 2 Dec 2011 11:36:41 -0400 Message-ID: Subject: Re: [PATCH 1/2] Provide return status in gatt_service_add function From: Anderson Lizardo To: Santiago Carot Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Santiago, On Fri, Dec 2, 2011 at 7:43 AM, Santiago Carot wrote: > When I was working in this stuff, I was wondering if there may exist > the case when a plugin registers several services and the last one > fails, Do you think it would have sense to provide the service ID as > return parameter to allow plugins remove their attributes before > aborting the loading operation?, On the other hand, this feature would > raise the posibility of finding gaps in the distribution of handlers > assigned in GATT due that plugins could add and remove services > dynamically, I'm not sure if that is expected in GATT. I think that, before doing anything like this, we should ensure the handles allocated for GATT servers do not change after registration (i.e. they are kept in storage and reloaded when bluez starts). If possible, can you contribute on this regard? Thanks, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil