Opened 21 years ago
Last modified 12 years ago
#1879 new Feature request
Transfer Top-Level-Dir+All Subdirs Before Next TLD
Reported by: | blujay | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | blujay | |
Component version: | Operating system type: | ||
Operating system version: |
Description
As it is now, when transferring directory structures,
FZ has a strange way of doing it. Instead of
transferring all files and directories in each
top-level directory, it seems to transfer some files
and dirs in each TLD, then goes to a "level two" in
each TLD, and then a "level three" in each TLD. At
least, that's how it seems.
A better way would be to transfer all files and dirs in
each TLD before going to the next TLD. For example,
consider this remote tree:
/
dirA
level1
level2
dirB
level1
level2
dirC
If that remote tree was transferred to the local tree
with FZ, FZ *should* transfer /dirA, /dirA/level1, and
/dirA/level1/level2 *before* transferring anything in
/dirB. It should then transfer everything in /dirB
before moving on to /dirC.
The reason is simple: if a transfer is aborted, and the
queue is lost (with FZ currently unable to export large
queues, this is a very real problem), you can easily
find what directories have been completely transferred,
and which ones have been partially transferred, and
proceed to transfer the rest. As it is now, if you
lose your queue, the only way to be sure you get all of
the files is to START ALL OVER AGAIN. When
transferring 30,000+ files totalling several GIGABYTES
in size this is VERY frustrating.
I hope that was understandable enough. If you need
more clarification, let me know.
Attachments (1)
Change History (3)
comment:1 by , 21 years ago
comment:2 by , 12 years ago
Component: | Other → FileZilla Client |
---|
That directory tree didn't come out right. Here's an image.