Issue activity log
| 2008-06-23 11:41 | Created | More precise keeping remote directory up to date |
| Component | General | |
| Severity | Enhancement | |
| Comment | WinSCP uses FindFirstChangeNotification API to receive notifications about changes in watched directory(is). This way it does not receive information about particular file that gets changed. To find out, it performs synchronization between the changed local directory and corresponding remote directory. This has following impacts: 1) Even non-changed files may get updated on remote directory, if the directories were not synchronized before. 2) Plain renaming of local file results in deleting original remote file and uploading new file. 3) Timestamps of local and remote files must be aligned. 4) Timestamp precision is important. Particularly with FTP, with precision of one minute, frequent changes are not uploaded, as the timestamp may stay the same. Solution is either to: 1) Remember last state of local directory(is) and compare new directory state against it (and not against remote directory) 2) Use ReadDirectoryChangesW API (available since Windows 2000 only). https://winscp.net/forum/viewtopic.php?t=5815 |
|
| 2011-02-28 10:40 | Comment | Issue 79 has been marked as a duplicate of this issue. |
| 2011-02-28 10:41 | Comment | https://winscp.net/forum/viewtopic.php?t=9463 |
| 2016-01-26 14:26 | Priority | Low |
| Comment | Improved by Issue 1395. Decreasing priority. | |
| 2016-01-26 14:40 | Comment | Emails with Jan Hajek in December 2015. |
| 2018-10-15 10:41 | Vote | 1× |
| Vote | 1× | |
| Vote | 1× | |
| Vote | 1× | |
| Vote | 1× | |
| 2020-10-23 13:25 | Comment | https://winscp.net/forum/viewtopic.php?t=30025 |
| 2021-04-12 09:58 | Vote | mihu999 |