[Standards] Images in chat

Peter Waher peterwaher at hotmail.com
Mon Mar 14 07:38:55 UTC 2016


Hello Goffi.
Thanks for your reply. Jingle file transfer can be negotiated using the HTTP over XMPP (XEP-0332) phase. The URI provided therein (http://xmpp.org/extensions/xep-0332.html#httpxscheme) allows parties to negotiate if file transder, in-band-bytestreams or jingle should be used for large content. Small content or dynamic content can be transferred using text, xml, base64 or chunked base64 methods.
Regarding XEP-0231: It looks like an interesting method, if HTTP over XMPP is not supported. BoB does not support partitioning the content file into smaller blocks it seems, but it includes a method for integrating the content into the chat sessions using XHTML-IM, which is what I'm looking for. Thanks.
Best regards,Peter Waher
> 
> 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
> 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20160314/710d020f/attachment.html>


More information about the Standards mailing list