-----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.
Why not?? It's very XHTML like. I'd say this is a good reason we choose XHTML and not some "more simple" custom layout scheme.
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).
That's an alternative. It's far from the only way. This method here is good for small images that are needed with a minimum of latency. And it's simple.
_______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
