[dcc2] Multi headers + metadata

[Phoenix Fyrestar]

here is a list of some things that could be usefull, some perhaps more than 
others.

senders user at host and ip address.  While the client should be able to handle 
this anway, it might come in useful

md5 or sha1 has - has been suggested by dave,  and I think this is a good 
thing.

file metadata like timestamp, permissions, mime type, character set,  
encoding,  etc.

compression token.  I was thinking that perhaps compression could be handled 
by having a token that would say that the sender supports compression.



On Tuesday 27 April 2004 05:35 pm, Dan Smith wrote:
> Hi everyone,
>
> 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?
>
> 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?