GATT Caching on Unicast Client

RE: GATT Caching on Unicast Client

dejans — Fri, 08 Nov 2024 11:35:28 GMT

Hi Omri,

Zephyr host does not do any actual caching. The application on the client side must store the handles themselves, handle reading database hash and receiving service changed indications.

Best regards,
Dejan

RE: GATT Caching on Unicast Client

Omri — Thu, 07 Nov 2024 19:04:31 GMT

Hi Dejan,

I’d like to clarify my previous question. Our application, which plays a central role, needs to reduce connection time by using the GATT caching feature.

The goal is to store a local copy of the remote database structure and reuse it during subsequent connections.

Is there anything specific the application should do before or during the connection process, or is it enough to simply enable `CONFIG_BT_GATT_CACHING`?

Regards,

Omri.

RE: GATT Caching on Unicast Client

dejans — Thu, 07 Nov 2024 11:03:16 GMT

Hi Omri,

Enabling CONFIG_BT_GATT_CACHING should be enough, just ensure that all dependencies are satisfied.

Best regards,
Dejan

RE: GATT Caching on Unicast Client

Omri — Wed, 06 Nov 2024 17:14:53 GMT

Thanks Dejan,

Should I only enable the GATT Caching by "CONFIG_BT_GATT_CACHING=y"?

RE: GATT Caching on Unicast Client

dejans — Wed, 06 Nov 2024 15:49:03 GMT

Hi Omri,

The issue with GATT Caching you are referring to is quite old. It was valid around the NCS v2.3.0 and it seems to have been fixed since then.
Please let me know if you see any issue with it when trying to use it in NCS v2.5.0.

Best regards,
Dejan