[JDEV] MIME-Version

[Scott Robinson]

And so would every other language the other way. This still reduces code in
general. I'm sorry for Java, though. (I might note not all Java apps have
access to javac.mail.internet anyway)

Scott.

* Patrick McCuller translated into ASCII [Wed, Aug 11, 1999 at 12:09:57PM -0400][<01fa01bee413$f5035360$1b76c897 at scylla>]
> 
> 	Aaron is 100% right on this one.  Have you looked at MIME-enabled
> libraries? Java's javax.mail.internet package is tied closely enough to
> RFC822 style email messages that it would be a hack at best to even use it
> to parse our half-kosher style.
> 
> 	It doesn't really make MIME easier to use, just different.
> 
> 	JabberBeans will have to write its own MIMEish modules, yay.
> 
> 
> Patrick
> 
> 
> > -----Original Message-----
> > From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> > Scott Robinson
> > Sent: Wednesday, August 11, 1999 11:30 AM
> > To: jdev at jabber.org
> > Subject: Re: [JDEV] MIME-Version
> >
> >
> > It is just a matter of placement. If we use the wrapping <mime/>
> > tags, then
> > the developer of a client using MIME not only doesn't have to worry about
> > writing extra (albiet miniscule) code to grab the lines, and they
> > also don't
> > (a bit nicer) have to worry about the unique boundaries. In
> > general, it just
> > saves time and makes MIME easier to use.
> >
> > Scott.
> >
> > * arh14 at cornell.edu translated into ASCII [Wed, Aug 11, 1999 at
> > 10:58:11AM
> > -0400][<Pine.SOL.3.91.990811105628.23671M-100000 at travelers.mail.co
> > rnell.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
> > > >
> > >
> > > _______________________________________________
> > > 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
> >
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev