Hi 2011/6/17 Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx>: > Hi, > > On Fri, Jun 17, 2011 at 8:22 AM, Santiago Carot <sancane@xxxxxxxxx> wrote: >> Just a note. If there is a full GATT API and we do BlueZ plugins over >> GATT (wich have their own D-Bus API as usual in BlueZ). The GATT API >> may be in conflict with those APIs exposed by those plugins because >> Applications will be able to use Attribute D-Bus one avoiding those >> APIs exposed by plugins. Do not? > > As long as all APIs use the same stack, there is no issue AFAIK. For > instance, if someone uses the Proximity D-Bus API and another > application does the same operation over the "generic" Attribute API, > both operations will be processed the same way inside the BlueZ GATT > stack (because they use the same functions internally). At least this > is the intended behavior, we don't do much testing like that :) > Yes, sure. the GATT API will allow applications to avoid use API provided for GATT based plugins. In this scenario there will be two ways to doing things. A) Using the plugin API and B)Through the GATT API. ... or in the worst case, an Application may use both. > Regards, > -- > Anderson Lizardo > Instituto Nokia de Tecnologia - INdT > Manaus - Brazil > -- 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
