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) >> </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> > > Except that I hate MIME. :-)
If Peter says so, then I will consider hating MIME, too. Just need to
find some reasons first ;)
> 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.
(As a side note, you can download email attachments on-demand with IMAP)
--
Maciek A: It's against natural order of reading.
xmpp:[EMAIL PROTECTED] Q: Why is that?
xmpp:[EMAIL PROTECTED] A: People answering above quoted text.
Q: What's the most annoying on newsgroups?
signature.asc
Description: OpenPGP digital signature
