[Standards] Proposed XMPP Extension: Jingle HTTP File Transfer
rcb at ceruleanstudios.com
Mon Feb 12 23:44:26 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>> Title: Jingle HTTP File Transfer
>> Abstract: This document describes a content type used for
>> transferring files with Jingle, using the Hypertext Transfer
>> URL: http://www.xmpp.org/extensions/inbox/jingle-httpft.html
>> The XMPP Council will decide within 7 days (or at its next
>> meeting) whether to accept this proposal as an official XEP.
> How is this related to jingle ?
> Looks more like a customization to oob ... we could actually fold
> the listing/preview into oob (or an extension) such that they are
> relevant to other modes of transfer too, not just http.
Because it's not really HTTP. It's using HTTP syntax over a pseudo-
TCP connection atop Jingle UDP, as I understand it.
iq:oob doesn't provide for a method to traverse firewalls, and while
S5B does (proxies), proxies aren't run widely enough. The idea here,
as I understand it from the earlier conversation, is to deprecate
stream-profile, S5B, IBB and all of that in favor of spurring
adoption of the Jingle streaming method. If clients use Jingle for
file transfer, then they'll be better able to adopt the audio/video
portions of Jingle too. The hardest work -- the transport -- will
already be done.
This can be used in other ways too, of course; you could hijack the
HTTP methodology to, for instance, embed images in XHTML-IM messages
('img' being theoretically supported) and share the image files
without having to upload them somewhere else first. Like AIM direct
connect, pasting images into the message window.
Rachel Blackman <rcb at ceruleanstudios.com>
Trillian Messenger - http://www.trillianastra.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
More information about the Standards