filesize [Was: Re: [dcc2] Multi headers + metadata]

Dave Johnson dave-dcc2-org at iroffer.org
Thu Apr 29 21:28:22 EDT 2004


codemstr at ptdprolog.net writes:
> Btw, large files (64bit addressing) is something the spec doesn't seem to 
> address at all? And it probably should. There needs to be some way to 
> determine if the Size= is 32bit or 64bit so that the receiver knows how to 
> interpret it. And, if it is 64bit and the receiver can't support 64bit, it 
> needs to know this so that it can reject it rather than receiving 2GB then 
> corrupting the file because the counter wraps around. 

I was going to bring this up too.  I'd suggest that DCC2 specify that
the size token MUST be intreperated as a 64bit unsigned value (or if a
client is incapable to decoding a 64bit value it MUST detect possible
overflow and decode upto whatever limit it has).

If the client cannot decode 64bit numbers or cannot accept a file that
big (no matter what that means, 2GB, 4GB, 64GB, or simply a configured
max or available disk space) it SHOULD reject it with a
ErrorTokens=size.

-- 
Dave



More information about the dcc2 mailing list