拥有原生的Andr​​oid BLE关贸总协定实现同步特性？ [英] Has native Android BLE GATT implementation synchronous nature?

问题描述

我记得读了<一href="http://img-developer.samsung.com/contents/authCdn/ble/Guide_and_Hints_for_Samsung_BLE_API.pdf?__gda__=1375430976_5fccae8604db7eb9b442186689e3381d">"Guide并提示 -doc到三星BLE API ：

  

之一的三星F表示最重要的概念/ W和S粘性是   它的同步性。也就是说，如果我们称之为例如   writeCharacteristic为特定特性，如果它返回   如此，任何BluetoothGatt或BluetoothGattServer方法的调用   在接收到onCharacteristicRead callbacķ后应做。   这是因为堆栈被设计成支持和过程只有一个   GATT通话的时间，如果，例如，你叫   writeCharacteristic的任何C haracteristic或readCharacteristic很快   在第一个之后，它会被忽略。

1. 这是否也适用于NATIV实现BLE的介绍 在安卓4.3？
2. 三星API也只支持一个连接关贸总协定设备一次。 已经原生API在这个变化？

解决方案

三星最近发布的同一页我在我的问题联系在一起的一个移民-document。他们完全回答我的问题，而比较新的原生API BLE与三星BLE API：

  

同步呐堆栈和F / W的TURE并没有受到影响。   也就是说，如果我们称之为例如，writeCharacteristic对于特定   的特点，如果返回true，接下来的任何BluetoothGatt电话   或BluetoothGattServer方法应的onCharacteri之后进行   sticRead回调接收。这是因为堆栈被设计   支持和过程仅一个总协定呼叫的时间，并且如果为   例如，您拨打writeCharacteristic任何C或readCharacteristic   haracteristic后不久，第一个，它会被忽略。

I remember reading in the "Guide and Hint"-doc to the Samsung BLE API:

One of the most important concepts of the Samsung F/W and s tack is its synchronous nature. That is, if we call for example , writeCharacteristic for a particular characteristic, if it returns true, the next call to any BluetoothGatt or BluetoothGattServer method should be done after the onCharacteristicRead callbac k is received . This is because the stack is designed to support and process only one GATT call at time , and if , for example , you call writeCharacteristic or readCharacteristic of any c haracteristic soon after the first one, it is ignored.

1. Does that also apply to the nativ implementation of BLE introduced in Android 4.3?
2. Samsung API also supports only one connected GATT device at a time. Has this changed in the native API?

解决方案

Samsung recently published a "migration"-document on the same page I linked in my question. They exactly answer my question while comparing the new native BLE API with the Samsung BLE API:

The synchronous na ture of the stack and F/W hasn’t been affected . That is, if we call for example , writeCharacteristic for a particular characteristic, if it returns true, the next call to any BluetoothGatt or BluetoothGattServer method should be done after the onCharacteri sticRead callback is received . This is because the stack is designed to support and process only one GATT call at a time , and if , for example , you call writeCharacteristic or readCharacteristic of any c haracteristic soon after the first one, it is ignored.

这篇关于拥有原生的Andr​​oid BLE关贸总协定实现同步特性？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！