Content deleted Content added
Waldemar7k (talk | contribs) |
Waldemar7k (talk | contribs) |
||
Line 87:
'''None''' of the open source software listed in the table (with the exception of Unison) has a true file rename/move detectability feature. If a file ''A'' was renamed to ''B'', a software with this feature should detect that file ''B'' on the first server/folder <u>is</u> file ''A'' on the second server/folder. However, most of the listed software can only detect that file ''A'' is missing on the first server/folder, and file ''B'' is missing on the second server/folder. Therefore, stating that those software has rename/move detectability feature is misleading. I'd advise using a third option – ''Partial'' – which mark that the software can only detect if a file is missing, but not if a file was moved. – <font face="Monotype Corsiva">[[user:Fuzzy|Fuzzy]]</font> – 12:14, 9 July 2013 (UTC)
I think the definition above the table is quite clear what Renames/Moves is supposed to be: mimic the operation on the other side. Handling them the same way as new/removed files (and therefore just copying it over) should be marked as "No", there is no need for "Partial". OK, maybe I missed something, so what would be the difference between a "No" and "Partial"? I tested the behavior of FreeFileSync, and can confirm that it does not detect moves and renames, as required by the definition here, it simply threats them as new files on one side, and to be deleted files on the other. However I am reluctant to change this, since I don't have any sources, just my own testing. Any advice what can be done here? - [[User:Waldemar7k|Waldemar7k]] ([[User talk:Waldemar7k|talk]]) 22:07, 20 December 2014 (UTC)
== Commercial vs Proprietary ==
| |||