Re: Any better solutions to BLE caching?
Re: Any better solutions to BLE caching?
- Subject: Re: Any better solutions to BLE caching?
- From: Etan Kissling <email@hidden>
- Date: Fri, 19 Apr 2013 09:36:04 +0000
- Thread-topic: Any better solutions to BLE caching?
|
Rick / Gareth / Arvydas
Apple points out the correct way to invalidate the GATT database cache:
Excerpt from https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf
The iOS device implements the GAP Service Changed characteristic, because the database contents can change at any time. The Bluetooth accessory should therefore support the Characteristic Value Indication of this characteristic and, upon receiving indications, invalidate
its database cache accordingly. See the Bluetooth 4.0 specification, Volume 3, Part G, Section 7.1.
Did not test this, but if it works, you should get a callback in the CBPeripheralDelegate (didInvalidateServices or something similar).
Etan
wrote:
I have this problem as well, I'd love to hear any solutions other people have found, or even a good specification of what is cached, where, so I can work around it!
_______________________________________________
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
|
_______________________________________________
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