My expectation was that every change/update during synchronisation goes through the queue -- including the ones in the "keep directory up-to-date" and synchronise fuctions. That the queue provides a way to control when updates are pushed live/across and a way to monitor the changes.
After all, that's the purpose that queues serve.
Now I'm not sure what the queue actually does, what purpose it serves. I take it that its role is limited to manual file transfers?
It's all a bit confusing, especially since the queue settings appear to be universal "transfer" settings in the preferences. That's what led me to think that something was wrong with my copy of the software, as no matter what I did, the changes performed during the two synchronise functions never passed through the queue, and I had no way to delay their immediate transfer until I have reviewed the changes to be applied.
What I'm missing is some way to track/queue the changes while using the "keep directory up-to-date" function, and to only push them live/across when I have personally reviewed them and approve them with the push of a button. Essentially, automatic edit tracking, and then a manual confirmation to push the changes across to the other side/server.
It's a more safe way to manage file transfers than leaving it up to the software to decide what needs to be pushed across when it wants to, and having no way to prevent unwanted changes to the server.
Reply with quote