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

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


Well, I've never seen a write-up of how PseudoTCP works, so it's not 
right for me to criticize it. HTTP seems like a fine thing, if you've 
already got a TCP (or PseudoTCP) connection.

Scott Ludwig wrote:
> Peter, can you articulate what the issue is for using HTTP for file 
> transfer?
> 
> PseudoTCP is simply a way to get reliability on a UDP packet stream
> (UDP is used because it can traverse NATs easily).
> 
> HTTP is actually quite flexible. There are many applications on the
> web that are based on HTTP, people are familiar with the programming
> model, and you can extrapolate other applications that can be built
> with it.
> 
> On 2/7/07, Peter Saint-Andre <stpeter at jabber.org> wrote:
>> That's a possibility. Though their HTTP over PseudoTCP over UDP stuff
>> scares me a bit. :-)
-------------- 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/d7a9bede/attachment.bin>


More information about the Standards mailing list