In case custom url logging is enabled and there is no network connection, the http requests are queued until the network connection is restored. In case the user is only interested in the most recent gps location, this can be disadvantageous because sending all the queued requests might take some time.
Example use case
Logging interval is 15 seconds.
Custom url logging is enabled.
There is no network connection for 3 hours.
A custom url call takes around 500 milliseconds.
This means after the phone has network connection again, it will take 6 minutes to send the queued requests. The most recent location will be sent at latest, at the end of 6 minutes.
Possible solution
To keep the current behavior for users interested in all logged locations and support also to only send the latest location, a 'Discard offline locations' toggle would be introduced on the Custom URL settings page. With disabled toggle, everything works as before.
If the toggle is enabled, only the latest location will be sent to custom url when the phone has network again.
Description
In case custom url logging is enabled and there is no network connection, the http requests are queued until the network connection is restored. In case the user is only interested in the most recent gps location, this can be disadvantageous because sending all the queued requests might take some time.
Example use case
This means after the phone has network connection again, it will take 6 minutes to send the queued requests. The most recent location will be sent at latest, at the end of 6 minutes.
Possible solution
To keep the current behavior for users interested in all logged locations and support also to only send the latest location, a 'Discard offline locations' toggle would be introduced on the Custom URL settings page. With disabled toggle, everything works as before. If the toggle is enabled, only the latest location will be sent to custom url when the phone has network again.