Hello, Jingle file transfer could be used for that with and "xmpp:" URI, but we still don't have Jingle URI (this would be easy to solve though). There is also XEP-0231 but it's more suitable for small images.
++ Goffi Le dimanche 13 mars 2016, 15:52:01 Peter Waher a écrit : > Hello Fabian > Thanks for your response. > > > > So, there are two things that are needed: > > > > > > 1) Transfer of the image content. This can be done in various ways. > > > 2) The receiver needs to understand the context, i.e. that the image > > > should be displayed in the chat window (not saved to file, shown in a > > > popup window, etc.) > > > > > > What solutions are available? I know I can solve this using XHTML-IM > > > (XEP-0071) and HTTP over XMPP (XEP-0332), if both are supported on both > > > clients. XHTML-IM allows me to include an <IMG> tag with a link to the > > > image using the httpx URI scheme (HTTP over XMPP). This scheme defines > > > where the image can be gotten, and negotiates how the image is to be > > > transferred. What I wanted to know is, are there any other alternatives? > > > > maybe the easiest way would be to use XEP-0363 (HTTP File upload) and > > then use XEP-0066 (Out of Band Data). > > > > As you mentioned, you could then also use XEP-0071 (XHTML-IM) instead of > > XEP-0066, but personally I would always prefer XEP-0066 and leave it up > > to the client implementation to decide how to display the file. > > That would require uploading the image to a third party, in this case an > HTTP server. That is undesireable. The image should be considered private > and shared only between the two communicating parties. I conclude that > there are no other ways than by using XHTML-IM and HTTP over XMPP. Best > regards,Peter Waher _______________________________________________ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
