[jdev] Re: XHTML-IM XEP implementation
stpeter at jabber.org
Thu Jan 4 14:08:43 CST 2007
Maciek Niedzielski wrote:
> Peter Saint-Andre wrote:
>> Maciek Niedzielski wrote:
>>> Peter Saint-Andre wrote:
>>>> Alexander Gnauck wrote:
>>>>> I would like prefer smth which allows multipart
>>>>> messages with different content types where plain text is always
>>>>> required. Content types could be plain text, xhtml, rtf etc...
>>>> Hmm, there are many issues with email to jabber translation (attached
>>>> files etc.). They are not easy to work out, but it would be interesting
>>>> to try. :-)
>>> If we want to replace email, maybe copy email's solution?
>>> I can imagine something like this:
>>> <message xmlns:content="....">
>>> <body content:type="text/plain">
>>> (plain text would still use body element to be backwards compatible)
>>> <content:part type="text/html">
>>> <html xmlns="......">.....</html>
>>> <content:part type="image/png" encoding="base64"
>>> disposition="inline" filename="x.png">
>> Except that I hate MIME. :-)
> If Peter says so, then I will consider hating MIME, too. Just need to
> find some reasons first ;)
To be more precise, I don't think that attaching files to email messages
is a smart way to transfer files.
>> Better, I think, for the sending domain to
>> store the attachment (WebDAV anyone?) and for the recipient to retrieve
>> the attachment via a well-defined file transfer method.
> But you still need a method to advertise the attachments somehow.
Sure. XEP-0066 or XEP-0137 or something like that. IMHO XEP-0129 could
come in handy here...
Jabber Software Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
More information about the JDev