Thing is I wanna create a queue that does A -> B -> C. Thus pausing transfer A to B after dir is created on B so I can disconnect from A and queue dir from B to C and then leave the computer unattended. After A to B finishes ffxp should take next item in queue (B to C) and transfer it, but dir contents is not refreshed on B after A to B finishes.
You waited until transfer A to B finished? Connected to C, manually refreshed B and then transferred B to C?
Would be great if ffxp refreshed once on source before starting the transfer of a queued dir - even if it is inside that dir when transfer is about to start. If client has been transferring files to that dir for 2 hrs on a slow connection and then has that dir already queued for further transfer to a third server it won't know exactly what the contents is. Note that this only applies when not using the ffxp dir cache, because the cache can update after every file transfer. No such options exists when dir cache is not used.
|