[JDEV] A piece of MIME? (possible alternate solution)
scott at tranzoa.com
Tue Aug 10 22:34:27 CDT 1999
Hmm, I like the way this solution is flows better than mine. I'd ask the
question of how we will make sure plain-text clients won't parse <mime> as
text, or are we de-facto'ing they won't?
I would also suggest the type "message/jabber" for forwarding a jabber
* Jeremie translated into ASCII [Tue, Aug 10, 1999 at 10:10:47PM -0500][<Pine.LNX.4.10.9908102151480.23715-100000 at lor.jeremie.com>]
> > Attached is a exerpt from my MIME document. It's still very raw, but I
> > believe the concepts are understandable. It is horribly full of useless
> > comments. CHEW ON THIS!
> I've read over the proposal, and I think I understand what you are getting
> at and the need for MIME, but I'm not sure about the approach :)
> I'm all for figuring out how to include the necessary MIME functionality
> in Jabber. IMHO I don't think we need the full capabilities of MIME, just
> the aspects that allow the encapsulation of alternate forms of the textual
> content, text/*. Anything beyond text/* isn't appropriately expressed
> within an XML stream anyway, and best left to file transfers.
> Of course, all of the encapsulated data is still appropriately escaped for
> XML so that conflicting tags aren't processed.
> What about a compromise? What if (as I think was suggested by Patrick) we
> include an optional tag that can be embedded within a message, for
> <say>This is BOLD!<mime type='text/html'>This is <B>BOLD</B>!</mime></say>
> This doesn't require any changes to the main protocol and will work with
> non-supporting clients. Basically, it's a way to express alternate forms
> of the same content, multiple <mime/> sections could be included in one
> <say/>, each with a different form of the content.
> Is this approach workable? Is there a middle-ground here?
> jdev mailing list
> jdev at jabber.org
More information about the JDev