-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ulrich Staudinger wrote: | Some further investigation and a very good hint from Heiner revealed this: | | http://www.armware.dk/RFC/rfc/rfc2397.html | | <IMG | SRC="data:image/gif;base64,R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAw | AAAC8IyPqcvt3wCcDkiLc7C0qwyGHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFz | ByTB10QgxOR0TqBQejhRNzOfkVJ+5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSp | a/TPg7JpJHxyendzWTBfX0cxOnKPjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJl | ZeGl9i2icVqaNVailT6F5iJ90m6mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uis | F81M1OIcR7lEewwcLp7tuNNkM3uNna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH | hhx4dbgYKAAA7" | ALT="Larry"> | | | Which comes even closer to my desired solution .... | I'd like to encourage client developers to implement this along with | xhtml support for pasting images from the clipboard into the chat.
Umm, that's not very Jabber like. Couldn't the img src be an xmpp URI that specifies an id of a file transfer in its query component? The precise sequence of steps would need to be elaborated (ie: send img first, then message; the other way?; or it doesn't matter).
There would still be the issue of sending inline images in offline messages. This could tie into the problem of offline file transfers and the push to talk idea I've been pushing.
- - Nolan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCZ0PHhuPszQVSPEARAicXAKCf3zRTus7AbUMSKlbCBwWBrgf1UACgnbH2 evTM/yMHoYrYP2nz2Wv7R0E= =hxzO -----END PGP SIGNATURE-----
_______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
