Hi This...
> <IMG > SRC="data:image/gif;base64,R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAw > AAAC8IyPqcvt3wCcDkiLc7C0qwyGHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFz > [...] > F81M1OIcR7lEewwcLp7tuNNkM3uNna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH > hhx4dbgYKAAA7" /> ..is really as much inline as it could be. I would choose a solution similar to MIME with <IMG SRC="cid:12345678";> and an additional <obj/> which contains the base64 coded image, IN THE SAME MESSAGE. I don't agree, that the Jabber way is defined by discoing and file-transferring everything. There are arguments for carrying images in the same message. Embedding images works equally well as embedding images by URL into MIME mails. They have a half-life period and after some time the external images disappear. If you want to archive complete messages with out the risk of loosing images, then the image data must be in the message. hw -- Dr. Klaus H. Wolf bluehands GmbH & Co.mmunication KG http://www.bluehands.de/people/hw +49 (0721) 16108 75 -- Jabber enabled Virtual Presence on the Web: http://www.lluna.de/ Open Source Future History: http://www.galactic-developments.com/ _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
