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
In the current schema only the kmz files are being transferred but from now onwords there will be a kmz file and there may or may not be a delta file associated with it.
If one kmz is transferred and if there is a delta file associated with it, then it should be transferred first then the other kmz file. We can think of as a container like a container contains a kmz and a delta file, which is being transferred now. The delta file associated with a kmz can be identified by the name of the delta and the kmz file.
For the transfer of delta these must be followed:
If receiver is already having the latest delta then it should not send the previous version
If receiver is not having the delta or having the older version delta than the sender's then the latest delta should be sent to it and previous version of delta should be deleted after the completion of the latest delta
The name of the delta and the kmz will follow the following example format:
kmz - TXT_priority_data_source_defaultMcs_lat_lon_timestamp_groupID_versionNo.kmz
delta -TXT_priority_data_source_defaultMcs_lat_lon_timestamp_groupID_versionNo_timestampOfDeltaCreate.delta
The text was updated successfully, but these errors were encountered:
If it starts receiving a new KMZ file then obviously it does not have a diff. So just download the KMZ file and enqueue any associated DIFF file in the receiving thread.
If it has multiple nodes in range then pick the latest DIFF file while syncing.
And for syncing the DIFF files, put a universal condition that only download a new DIFF if it is newer than the present diff
both KMZ and diff are having timestamp and number. But the kmz contains the timestamp of the creation and the diff contains the timestamp of creation as well as timestamp of modification
See the format of both the files as mentioned in the above comment.
It will be followed strictly in our app
In the current schema only the kmz files are being transferred but from now onwords there will be a kmz file and there may or may not be a delta file associated with it.
If one kmz is transferred and if there is a delta file associated with it, then it should be transferred first then the other kmz file. We can think of as a container like a container contains a kmz and a delta file, which is being transferred now. The delta file associated with a kmz can be identified by the name of the delta and the kmz file.
For the transfer of delta these must be followed:
The name of the delta and the kmz will follow the following example format:
kmz - TXT_priority_data_source_defaultMcs_lat_lon_timestamp_groupID_versionNo.kmz
delta -TXT_priority_data_source_defaultMcs_lat_lon_timestamp_groupID_versionNo_timestampOfDeltaCreate.delta
The text was updated successfully, but these errors were encountered: