ya this looks nice.
AS also Peter mentioned the problem will be the binary inline content if
it's getting to big. Then receiving this message blocks your whole XMPP
connection. For small inline content (small images) this will work fine.
A workaround for this problem is to send the "main client connection"
only a notification for big messages and download them in additional
connections. So you main connection can still receive stanzas while
downloading a big stanza (or multiple smaller chunks).
Alex
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)
</body>
<content:part type="text/html">
<html xmlns="......">.....</html>
</content:part>
<content:part type="image/png" encoding="base64"
disposition="inline" filename="x.png">
...............................
</content:part>
</message>
