Brendan wrote:
If you were going to do that you may also want to add a "from" field to the directory entry, containing a URL (e.g. ftp:://somewhere.org/files/theFile.exe).
Quote:
... or a "backup on" field, pointing at the description of the CD where things were back-up'd
Good idea, I was already thinking about that.
Those fields could simply be one field.
At least one or two backup fields (yeah, both internet urls or CD field) should be enough, I think.
So now it would look like this:
(with some modifications, like cluster size should be 8 bytes, 64 bit)
[table][tr][td]deleted(1)[/td][td]filename[/td][td]0[/td][td]size(8)[/td][td]priority(1)[/td][td]cluster(8)[/td][td]backupreference[/td][td]0[/td]
[/tr][/table]
But now I have a question, what if a user deletes one file.
And he creates a file, in the same directory of course.
What should I do ? overwriting it or adding it ?
If adding it, then the directory list could becoming HUGE!
If deleting it, the backupreference won't be needed.
Should I give the user the ability to do that ? or should I use the priority bit ([me=DennisCGc]thinks that should be better
)[/me]
DennisCGc.