B4J Question Using live-location over cloudkvs

[schimanski]

I made some apps with live locations like whatsapp does. I tried it with websockets and now, I made it with cloudKVS. With cloudKVS, the clients sends the data every 750ms to the server. That runs without problems and very smooth, but i don't tested it with more than 15 devices. Did somebody had some experiences with such a soltuion up to 100 or 150 devices? Perhaps there are other soltuions for that. Thanks for every experience...

 

[Erel]

It is always a good idea to make some stress tests. You can implement a small test with B4J and run multiple instances.
You can see some numbers here: https://www.b4x.com/android/forum/threads/server-performance-measures.37502/#post-238853

Why do you need to send the data every 750ms? Can't you collect multiple locations and then put them as a single object?

A nice feature of CloudKVS is that even if the server is too slow or unavailable, the data will not be lost and it will be eventually synchronized.

 

[schimanski]

Thanks, Erel.
I don't want to track the way of the device. It is important to know the current location of device with low latency. The clients refreshes the users every second and with an sending intervall of 750ms, it is a very smooth solition and the users don't have to check the device from time to time...It runs the whole time without checking a server connection...
I made an other solution with websockets, but it is not so reliable. The device sometimes looses the server connection.

 

[Erel]

If you only want to know the current location then there is no reason to use CloudKVS. Use jRDC2 instead. It will be simpler and perform better.