[JDEV] MIME-Version

[arh14 at cornell.edu]

What is more efficient than constructing a MIME message from XML, is just 
taking the preconstructed MIME message.  Why separate out the headers, 
stick them in the tag, and then have the client take them back out of the 
tag and construct the message??

MIME is just a chunk of text.  Let the client deal with it.

Aaron

On Wed, 11 Aug 1999, Scott Robinson wrote:

> It isn't "outside" the MIME body. We're not dealing with straight MIME
> because (one of the reasons) it would be more efficient to place it straight
> into the <mime/> tag. The <mime/> tag is part of the body, and can be easily
> constructed into a proper MIME message (for those that want it) with the
> rest of the message/jabber.
> 
> Scott.
> 
> * Dave Smith translated into ASCII [Wed, Aug 11, 1999 at 09:37:30AM -0500][<NDBBJJODKKLCELCEPIEMIEDHCAAA.dave at dorm4.org>]
> > >
> > > I'm assuming, then, that just sticking the MIME chunk in the <mime> tag
> > > isn't going to be done?  Why use XML attributes for MIME headers when you
> > > can just put the MIME headers in the MIME chunk??  MIME already contains
> > > all it needs to describe itself.
> > >
> > 
> > Hmm...this is a good question. Why in the world does the manipulator(client,
> > transport, whatever) have to be able to access the MIME attributes outside
> > of the MIME body? Isn't the whole idea of MIME to be self-describing?
> > <raised eyebrow>
> > 
> > D.
> > 
> > 
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>