scott at tranzoa.com
Wed Aug 11 09:52:21 CDT 1999
Except it won't be "parsing" MIME. It stays in XML.
* arh14 at cornell.edu translated into ASCII [Wed, Aug 11, 1999 at 10:25:14AM -0400][<Pine.SOL.3.91.990811102319.23671J-100000 at travelers.mail.cornell.edu>]
> Finally I am caught up with the messages. I still didn't get the
> reasoning for taking out all the mime headers and putting them in as
> attributes to the <mime> tag. If the client knows that this tag contains
> MIME, it just parses the MIME stream as usual. Any existing MIME library
> will be able to do this. By extraditing these headers into the <mime>
> tag, the client now must collect those headers for itself, and then
> resume MIME parsing. Why is this being done?
> On Wed, 11 Aug 1999, Thomas D. Charron wrote:
> > On Wed, 11 Aug 1999 00:27:23 Scott Robinson wrote:
> > >MIME-Version is required at the beginning of a MIME encoded message. Any
> > >suggestions as to the location? "<say MIME-version=1.0>"? Or will we just
> > >ignore that piece of the standard and assume version 1.0?
> > Attribute of the MIME tag itself?
> > ---
> > Thomas Charron
> > --== Sent via Deja.com http://www.deja.com/ ==--
> > Share what you know. Learn what you don't.
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> jdev mailing list
> jdev at jabber.org
More information about the JDev