All, By the authority vested in me by myself, I hereby decree that MetaData shall be in HTTP header format, as defined in RFC 1945. This is mainly because I cannot see any reason not to follow this established standard.
So, the key of the key/value pair is before a ':' and the value is after, e.g. Content-Type: text/plain These are the field names I have defined so far - taken directly from RFC 1945: Content-Type - the MIME type of the file contents Content-Encoding - the character encoding ------------------------ I propose to start a document containing the above information, and put it in the website area of CVS. People will be able to add any field names they feel are necessary or useful to this document. At some indeterminate time in the future we will review the document and make it official. Field names should follow RFC-1945 and friends unless it's for a concept that doesn't exist in the RFCs. It should be possible in proxies like FCRC to take the MetaData and add it to the HTTP header. So that's the plan -- unless you guys think this is a crap idea, of course. Steve _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
