[JDEV] A piece of MIME? (possible alternate solution)
scott at tranzoa.com
Wed Aug 11 01:29:15 CDT 1999
* Jeremie translated into ASCII [Wed, Aug 11, 1999 at 01:10:45AM -0500][<Pine.LNX.4.10.9908110107110.23715-100000 at lor.jeremie.com>]
> > Great!
> > I suggest we add several optional attributes to the <mime> tag,
> > MIME-Version,
How will we be using MIME-Version?
> > Content-Type,
> > Content-Transfer-Encoding,
> > Content-ID,
> > Content-Description.
> Absolutely, looks great except for Content-Transfer-Encoding. My
> understand is that this is used to represent content that has been encoded
> in another format, such as gzip. Since that's not legal in an XML stream,
> I'm not sure that aspect of MIME or attribute could be used. Correct me
> if I'm wrong though, I'm no expert :)
I can see a couple users for Content-Transfer-Encoding.
It has the potential to help us out in the charset wars. I'll quote from RFC
The encoding mechanisms defined here explicitly encode all data in US-ASCII.
Thus, for example, suppose an entity has header fields such as:
Content-Type: text/plain; charset=ISO-8859-1
This must be interpreted to mean that the body is a base64 US-ASCII encoding
of data that was originally in ISO-8859-1, and will be in that character set
again after decoding.
It can also take care of small data transfers. The following is also a
quote from RFC 2111:
Content-Type: Text/HTML; charset=US-ASCII
... text of the HTML document, which might contain a hyperlink
to the other body part, for example through a statement such as:
<IMG SRC="cid:foo4*foo1 at bar.net" ALT="IETF logo">
Content-ID: foo4*foo1 at bar.net
Finally, it just puts us one step closer to a complete implementation.
> Everything else looks great though!
> jdev mailing list
> jdev at jabber.org
More information about the JDev