[dcc2] MultiFile Transfer Headers

[Deryk Robosson]

On Sat, 2004-05-01 at 03:08 +0000, codemstr at ptdprolog.net wrote:
> > Let's say I recompile my program but forget to change the version 
> > number, and I send someone the executable. Then I realize I have 5 
> > different files named ViRC.exe and I may have sent the wrong one. If DCC 
> > keeps the modified date, I can say "Is that executable from today or 
> > last week?"
> 
> Ok I can see the usefulness there. I'm just not so sure the usefulness that 
> that brings outweighs the confusion it will also bring. Meaning, what happens 
> if it is from neither today, nor last week, but from tomorrow? Also, since 
> you can't change the creation times, you have:
> 
> Created: 02:00 Apr 30 2004
> Modified: 03:43 Mar 13 2004
> 
> So people will be confused by the fact that, yes ViRC.exe was modified a week 
> ago, but it was created today. How can you modify what has not been created 
> yet?

  I'd have to agree with codemstr on the time stamp issue.  It is not
relevant to the transfer of a file in any format.  The client itself can
enable the user with the option of stamping the filename or logging to a
file which has nothing to do really with the transfer itself.  Time
stamping and permissions should best be left to the operating system and
its underlying filesystem(s).

-- 
Deryk Robosson <deryk at 0x0a.com>