From: James T. <zak...@ma...> - 2016-01-14 19:39:15
|
> On 14 Jan 2016, at 11:34, wki...@gm... wrote: > > however, the above references to the .terrasync_cache files brings me to > something that i've only recently noticed and not asked about pertaining to > them... mainly wondering what their use is and if they need to be in every > terrasync directory... i use terramaster and i don't think that it updates those > cache files which means that even using terramaster, it i have the latest and > still have terrasync turned on, the same files will be downloaded again because > the cache file was wrong... if i'm thinking about that in the right manner... > i'll try to take a look at my debug logs and see if i see the same on this linux > installation... The intention is to migrate to a pure HTTP solution for TerraSync (instead of SVN) after 2016.1 is released, since this will give us many more mirroring and hosting options. The cache files are tiny and reflect the current revision of each file in the local copy; they’re analogous to the data a real SVN client stores in its ‘.svn’ directory in the root of the checkout. I expect the pure HTTP solution will need some very similar files to record the HTTP cache stamps of files it downloads - either one file at the root of the tree, or per-directory. (There’s advantages and disadvantages to both). Kind regards, James |