[Standards] Proposed XMPP Extension: Jingle File Transfer Description Format

Peter Saint-Andre stpeter at jabber.org
Wed Feb 7 17:37:29 UTC 2007

Mikael Magnusson wrote:
> Peter Saint-Andre wrote:
>> Remko Tronçon wrote:
>>>> For my next trick, a bytestreams transport, then an informational
>>>> "here's how to get started and put it all together" doc.
>>> A couple of questions:
>>> - How about a one-directional HTTP-like transport (like Google uses)
>>> to transfer the files? 
>> That's a possibility. Though their HTTP over PseudoTCP over UDP stuff 
>> scares me a bit. :-)
> What about HTTP over real TCP over IPv6 (native, or over Teredo or 6to4)?

Well once you've got a TCP connection (direct, mediated, pseudo, teredo, 
whatever) then using HTTP seems like a fine idea. And as I say, I've 
never seen documentation of Google's PseudoTCP stuff so it's not right 
for me to criticize it, maybe it's a thing of beauty. :-)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070207/10d0bcd1/attachment.bin>

More information about the Standards mailing list