Question about characteristic value transmission from a peripheral
Question about characteristic value transmission from a peripheral
- Subject: Question about characteristic value transmission from a peripheral
- From: Richard Lipes <email@hidden>
- Date: Wed, 20 Nov 2013 18:19:43 -0800
- Thread-topic: Question about characteristic value transmission from a peripheral
I have a question about transmitting a characteristic value from a PeripheralManager object. Suppose I have received a callback peripheralManager:central:didSubscribeToCharacteristic. I can start sending the characteristic value with the method updateValue:forCharacteristic:onSubscribedCentrals. It is possible the entire vale will not be sent (as a queue may be filled) in which case I will subsequently receive a callback peripheralManagerIsReadyToUpdateSubscribers which allows me to send additional “chunks” of the characteristic value with another call to updateValue:forCharacteristic:onSubscribedCentrals.
My question is, “Am I guaranteed that the CoreBluetooth Framework will NOT issue an additional callback peripheralManager:central:didSubscribeToCharacteristic between the first peripheralManager:central:didSubscribeToCharacteristic callback and a followup callback peripheralManagerIsReadyToUpdateSubscribers”? If there is no such guarantee, is there any recommended coding practice for handling this situation with a single PeripheralManager object or (even more complicated) for multiple PeripheralManager objects? It seems to me that some sort of ordered queue handling is required.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden