pepo wrote:

I would like to ask if there is a particular feature... Imagine following:
...

Thanks for your suggestion. It's unlikely this gets implemented though.

You can exclude the "B" folder from synchronization using file masks.

Hi,

I would like to ask if there is a particular feature... Imagine following:

1) I have 2 folders (A,B) and 10 files in each folder on webdav.
2) I will sync the whole webdav to local disc.
3) After sync I will create new folder (C) with 4 files on webdav and
4) I will delete folder B (or move to another place) on local disc and
5) 1st 4 files of folder A and 1st 2 files of folder B on webdav will be overwritten with newer versions of file (for example log files).

On next sync I would like to have option, where only following files would be proposed to sync from webdav to local disc:
1) Folder (C) with 4 files on webdav
2) 1st 4 files of folder A and 1st 2 files of folder B on webdav, because these are more recent than on last sync.

The rest of the files on folder B should not be synced, because these files are not more recent than on last sync and it shouldn´t matter that these files are missing on target local disc.

Probably some log file of successful transfers (with date and md5 checksum) has to be implemented, to which has to be compared on every sync.

Hopefully you understand my post, if questions please ask.

kind regards

peter

Awesome, thanks!

Just a follow-up thought: I imagine there will need to be a a checkbox or button to refresh the cache.

Thanks for your suggestion.
Will see if more people ask for this.

On some large sites and/or slower connections, it can take several minutes just to diff the files between local <-> server.

Can we have a feature to cache the diff data for the server files on the first run of the Synchronize feature for each session profile, so that consecutive runs can just diff the local files with the cache?