Closed rifatmahmud closed 8 years ago
Yeah, this comes down to the new cache solution. The read operation is still available, but you'll risk getting the NRF_ERROR_NOT_FOUND
if it's not in the cache.
If you want to mitigate this, you have two options:
RBC_MESH_DATA_CACHE_ENTRIES
#define.If you have a cache size larger than the range of handles you're using, the behavior will be exactly as before.
Can you please point me to the specific of this cache solution? Is this change applicable to the whole mesh service?
Got the explanations on the release notes. Should have looked at there first. My bad. :)
Hi, sorry about the long response time on this last issue, let us know if you have any further questions :)
Has the latest change removed the previous features of adding handles and having both read and write capability on each handle? If it is changed, please, suggest a way how to get the old feature back.