[Prev][Next][Index][Thread]
Content-encoding and external message converters?
-
To: Henrik Frystyk Nielsen <frystyk@w3.org>
-
Subject: Content-encoding and external message converters?
-
From: kennykb@cobweb.crd.ge.com
-
Date: Thu, 11 Jan 96 22:04:03 -0500
-
Cc: www-lib@w3.org
-
From kennykb@cobweb.crd.ge.com Thu Jan 11 17: 13:46 1996
-
In-Reply-To: frystyk@w3.org's message of Thu, 11 Jan 96 15:50:33 -0500. <9601112050.AA12630@www20>
-
Message-Id: <9601112204.AA29289@cobweb.crd.ge.com>
-
X-Face: 5*Bwl\0iY*1'W~D~c2foEA#,\H[\j3:fTgL0QDgl'0/_fV8X|GO>!b`fdiNc{Ioj6u7a{qq 1h+JHjg)m(|axb2m&0{I9cl5lQ9OeK\vdx=Ca]v9No,e'd~rIQ'ei,%J!^+@w|2/fLdXMKEOIh85kr plx|`3lxhu#KWB;}OjDeAg^
-
X-Uri: http://ce-toolkit.crd.ge.com/people/kennykb.html
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
References: