[Standards-JIG] Inline Images for JEP-0071: XHTML-IM

[JD Conley]

A xmpp: pull file transfer URI/IRI/whatever would be nice. Of course
this brings about changes I've talked about in the past where the
recipient can request a known stream id from a file transfer sender.

Also, in-band bytestreams works great for this, as long as it isn't a
huge amount of data, and take no time to setup.

-JD

-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Peter Saint-Andre
Sent: Tuesday, August 29, 2006 12:46 PM
To: Jabber protocol discussion list
Subject: Re: [Standards-JIG] Inline Images for JEP-0071: XHTML-IM

Andreas Monitzer wrote:
> On Aug 29, 2006, at 17:33, Peter Saint-Andre wrote:
> 
>>>> http://wiki.jabber.org/index.php/XHTML_Inband_Images
>>
>> Do you prefer that solution to the data: URI?
> 
> Both methods are actually best suited for different tasks.
Establishing
> a file transfer has a much larger overhead and latency, and is is
likely
> to fail when using NATs. It's only worth it for larger images. For
> smaller ones, a reliable in-band transfer is better.
> 
>>> It would be nice if this would become a JEP, so
>>> other people (like me) could actually find it :) After all, this is
>>> something that has to be specifically implemented into all
>>> JEP-0071-supporting clients to work.
>>
>> The JEP Editor is always open to receiving proposal submissions. :-)
>>
>>> The other part (disco#info feature for the data protocol) is not
solved
>>> by this, though. This could even be used for that thumbnail proposed
on
>>> that wiki page.
>>
>> Sure, we'd specify that in the proposal.
> 
> Ok, I'll try to come up with something. This JEP should probably
include
> both methods, since they're trying to solve the same problem.

Great, thanks!

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml