[dcc2] Multi headers + metadata

[Jesse McGrew]

Dan Smith wrote:

> It appears that we have come to a consensus regarding XML.  It would 
> require many authors to add additional dependances to their projects, 
> and may hinder adaptation.  MIME/HTTP style headers are simple to 
> parse and can mimic the same data structures that xml can (with clever 
> work).  If they are good enough for http and SIP, I am sure we will 
> not have a problem with them.  What do you think about this type of 
> representation for our header metadata?

Sounds good; it can be parsed simply by splitting and trimming 
whitespace. I agree that we shouldn't require features that will 
increase dependencies.

> Speaking of metadata, what additional information should we 
> standardize?  Under the current transfer proposal, we need a unique id 
> for each file listed in a header, file name+path, and size.  Any 
> additional information such as md5 hash, description, your ideas, 
> etc.. can be optionally included.  Any ideas as to what other metadata 
> would be useful to client authors?

Content type (not all systems determine a file's type by its extension, 
and some extensions are ambiguous)
Codec (for audio/video)
Length in seconds (ditto)
Origin (web site or person who supplied the file)
Version?
License/copyright notice?

> What about the transport?  Right now the idea is to create one 
> connection and send the header information, then request the files one 
> at a time over this connection.  They will be sent in the order that 
> they are requested.  This seems clean and simple.  Are we in agreement 
> on this or are there other ideas out there?

Sounds good.

Jesse
http://visualirc.net