You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 27, 2024. It is now read-only.
When running in an on-line streaming mode that sends locations to the server in real-time (vs. a batch update at the end of the day), it would be useful to have a cache of locations, so we aren't initiating communication on each location update.
When running in an on-line streaming mode that sends locations to the server in real-time (vs. a batch update at the end of the day), it would be useful to have a cache of locations, so we aren't initiating communication on each location update.
The intelligent caching we've implemented in the past is "Adaptive Location Data Buffering" that also uses TCP and UDP, although USF owns a patent on this technology:
https://www.locationaware.usf.edu/ongoing-research/technology/adaptive-location-data-buffering/
A simpler buffering mechanism would be to just cache X locations and dump them via TCP to the server.