This will allow me to optimize my reading time.
Thank you!
/!\ /!\ /!\ /!\ /!\ EDIT /!\ /!\ /!\ /!\ /!\
It’s good I got the answer. In fact, I saved my datas badly.
So, I have another question: Is it possible to read a few keys instead of all (example: the keys of index 0 and index 2) because the key of index 1 is for an image (base64), and this image is very long to read so I would first read all the others, display them and then read the image and display it afterwards.
Is it possible to read a few keys instead of all (example: the keys of index 0 and index 2) because the key of index 1 is for an image (base64), and this image is very long to read so I would first read all the others, display them and then read the image and display it afterwards.
Currently, there’s not. Interestingly enough, on the firmware level, that’d be possible to do, but our SDKs at this time always read all of the data. We would also have to use something else than JSON for serialization.
Ok because when I read all of the JSON content in my beacon, It lasts 2 minutes 12 seconds (for iOS) and 6 minutes 30 seconds (for Android) and I don’t see how resolve it.