- From: <kennykb@cobweb.crd.ge.com>
- Date: Thu, 11 Jan 96 22:04:03 -0500
- To: Henrik Frystyk Nielsen <frystyk@w3.org>
- Cc: www-lib@w3.org
frystyk@w3.org (Henrik Frystyk Nielsen) said: > The MIME parser stream takes out the metainformation and adds it to > the anchor. When all the metainformation is parsed, thestream goes > into transparent mode and lets the body pass untouched. This comment raises something that I don't understand with the stream stack protocols. There doesn't seem to be any means of handling conversions that relate to encodings and other envelope information. I'd like to expand the MIME parser to handle headers like Content-Transfer-Encoding: base64 -or- Content-Type: message/partial -or- Content-Type: message/external-body but I'm at a loss how to go about it with the stream plumbing that now exists. I'd also like to see support for the RFC1867 header line: Content-Disposition: form-data; name="xxx"; filename="yyy" but that looks easy to do using HTMIME_register. -- 73 de ke9tv/2, Kevin KENNY GE Corporate Research & Development kennykb@crd.ge.com P. O. Box 8, Room KWC273 Schenectady, New York 12301-0008 USA
Received on Thursday, 11 January 1996 17:13:46 UTC