[dcc2] MultiFile Transfer Headers

[Dan Smith]

Hi everyone,

So we have agreed (yes?) that XML will not be used for the file 
listings.  So far here is the list of agreed upon headers.  I believe that 
we can designate x-something headers to be client specific, and if they 
become popular enough add an official header for that item.  If you have a 
needed header, please mention it now so we can specify it in the draft.

Some people have mentioned content type specific headers in addition to a 
description field.  How do you all feel about this?  And if you think it is 
a good idea, what metadata would you like to associate with specific 
types?  For example, a photo from a digital camera could have date taken, 
photographer, camera model, location, (any thing in a Exif header), 
etc.  This could significantly expand the size of our draft.  Good or 
Bad?  How much metadata is needed?

MultiFile Header:
A list of new line separated name value pairs.  File segments are separated 
by a double new line.

Required Fields
===============
id: <file id number>
A unique value in this header, used to request a file.

name: <relative path + file name>
A relative path and file name.  path is needed for uniqueness in a multi 
file send, and path security issues should be checked by the client

size: <file size in bytes>
string representation, should check for overflow of 32 or 64, depending on 
client's platform

Optional Fields
===============
description: <file description>

sha1: <SHA1 file hash>

content-type: <file content type>

created: <file created timestamp>

modified: <file modified timestamp>


File permissions are a bit tricky, since each platform can specify them in 
a different manner.  Any suggestions?

I will be away for the weekend, when I get back I will update the 
multi-file document to remove the xml references and update it with out 
latest work based on your comments to this!

Cheers!
Dan


---------------------------
Dan Smith
+1 608-213-2867
Algenta Technologies, LLC