[JDEV] A piece of MIME? (possible alternate solution)
arh14 at cornell.edu
arh14 at cornell.edu
Wed Aug 11 09:13:09 CDT 1999
This is a plausible solution. However, I don't think MIME even uses "<"
or ">" so the only escaping you'd need to do is the same as any normal
escaping for any plain text message that might come through.
A chunk of MIME is still easier to convert to and from than XML tags.
For instance, if you were sending to an email target, you could just copy
the MIME chunk and send it of...no translation necessary. Using a chunk
of MIME also wouldn't affect the protocol.
On Tue, 10 Aug 1999, Jeremie wrote:
> > 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