|
Titel: [ftpsfv] Minor issues Beitrag von: element-x am 02. April 2004, 14:28:56 When other sites leave tagged directories such as:
-[sitename]-[all-crc-100%-ok]-[username]- Is it possible to have ftpsfv detect these? especially since now ftpsfv will create a second director of this same type. Also, when resuming an upload on an existing file that is marked as "bad", and I complete it, the tagged directory remains with 1-BAD, and also creates the [all-crc-ok] tagged directory. A feature request would be: Instead of creating a new file for "bad", can we just rename the existing file to "foofile.fooext.bad", or would this cause problems? I have just seen it in other sfv checking modules before. (Not really needed, but wondering if it would ever be an option perhaps). Titel: Re: [ftpsfv] Minor issues Beitrag von: TL am 02. April 2004, 23:00:20 Zitat von: "element-x" When other sites leave tagged directories such as: -[sitename]-[all-crc-100%-ok]-[username]- Is it possible to have ftpsfv detect these? especially since now ftpsfv will create a second director of this same type.[/qoute] Yes thats no problem, what do want to do then? Delete the other directory? Zitat von: "element-x" Also, when resuming an upload on an existing file that is marked as "bad", and I complete it, the tagged directory remains with 1-BAD, and also creates the [all-crc-ok] tagged directory. A feature request would be: Instead of creating a new file for "bad", can we just rename the existing file to "foofile.fooext.bad", or would this cause problems? I have just seen it in other sfv checking modules before. (Not really needed, but wondering if it would ever be an option perhaps). Another yes ;) I could implement this in the next version... Titel: [ftpsfv] Minor issues Beitrag von: element-x am 03. April 2004, 00:40:52 As far as old tagged directories left by other users, yes I would like to have them removed (no sense in having it there, if it doesn't provide up to date information).
To make sure you're not removing a directory with files, you could also test to make sure that it is empty before removing. (though I'm sure you would have thought of this already). About the .bad files, I just don't like having 2 copies of the files, though I can see why it's there. So you can resume the existing copy if need be. Though if this is an option that is possible to take advantage of, then that would be interesting. |