Google Talk File Transfers
Peter Saint-Andre
stpeter at stpeter.im
Mon Jun 17 15:05:21 EDT 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/17/13 3:42 AM, Phil Hannent wrote:
> Hi Ashish,
>
> I noticed that you are going to look at the Google Talk File
> Transfers. I was looking at the Jingle ICE communications a couple
> of months ago. I thought I should let you know what I found out
> before I moved on.
>
> There is the standards based Jingle way of doing things which
> Pidgin implements: http://xmpp.org/extensions/xep-0176.html
That spec was deferred for lack of activity (and the fault is mine
because I'm the author). If you have any implementation feedback,
please send it along!
> Then there is how GTalk actually implements its own Jingle session
> initiation: https://developers.google.com/talk/call_signaling
>
> Where I got to is that the <transport> element with the standards
> method, sends the transport candidates at the initiation and then
> Pidgin automatically expects them to be returned in :
>
> http://hg.pidgin.im/pidgin/main/file/00e6d5d4c37f/libpurple/protocols/jabber/jingle/jingle.c
>
>
http://hg.pidgin.im/pidgin/main/file/00e6d5d4c37f/libpurple/protocols/jabber/jingle/transport.c
>
> However with the Google method they will arrive later. Whilst I
> was looking at it for initiating a video conversation from my Phone
> to Pidgin I assume that P2P file transfers also happen over ICE.
Do you mean that Google uses ICE-TCP to signal the IP/port
combinations for file transfer? I really doubt that they chunk the
file itself over ICE, but you never know. ;-)
Peter
- --
Peter Saint-Andre
https://stpeter.im/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRv13xAAoJEOoGpJErxa2pt5UQAK29/FmqlfqsGM2c9UeInqdV
Xij+Gc09A6yb8qcN9FgngIz92sjZiVOE4AY6FmHmuIHVVFd+1L5mDrXtIKc4RNkY
nFNgIcYivM6zFmH0C3NlCQesQR0+Snrm2BFqb8eXRFo1AlxCe4rZtJyyksq74Ts3
2aFbEcsxr2OCFCI5hkYXHH5VstgAQ1ZstZCJWzyi8bWf2FU6HwnG4uy5cXbG4/xE
DHZ1f1w7PBf+4fwg5DBPEzNFakxA036vZq6FQyQ1RChYU6Tnt5XFCnJ7MLFKuPTh
JwPT4oHg3+BFIRqOhsOVYJGkWM93w41ZDcNivoGxQtiVaKSeJNVoqGHkE8FGiWH1
2yNMsHgNHd2phq9eu3736oVk/FWYUK5rRcoXWAzB3Cig2uk6zwYHXaoBC4CO2tmo
7udTgJLaR8wyIsCx7b6fyIZVHCFmXCJb8xgAXwcDuHd72lMA8HdLxfQ8IMXfgyWD
Y8fcajycwbxAf9/i26suuK62Bz1HgkiSTy1euANs8LMaIflCksVJjjJIwg7wFMfl
pUj4B1b9zlVDx3xHcZFSPKcMh1ac+RjFPWg5AVs5CRxqHUYX9P2PkP1+T6x/l72/
Y4b4iIH54SMQ9gw5xnw+Ycl3wxtIyYrTUuNyiRGGe8dL7EtRRS2ie+t5HMIreRc/
s7YxfcUw5LguEPqqbL6A
=OWYE
-----END PGP SIGNATURE-----
More information about the Devel
mailing list