[Standards-JIG] What's behind GTalk file transfer?

[Brian McBarron]

A more efficient way to generate a log is to run the app the following
arguments:

   /log verbose tstamp thread file

This will create a complete log on your desktop, and is not truncated or
compressed the way that a diagnostic log is.
(if you want to see debug output on the fly, replace "file" with "debug")

Regarding earlier questions:

We're not following an existing JEP, because we wanted to take advantage of
the jingle connection mechanism for file transfer.  A draft JEP on what we
are doing should come along shortly.  In the meantime, I can tell you that
file transfer consists of several layers.

Connection/Session management:  jingle
Reliability (change something udp-like into something tcp-like): pseudotcp
Transfer protocol: http

pseudotcp is not documented anywhere currently.  It was first used for
reliability in Picasa's Hello IM/Photo-sharing application for a similar
purpose.  We have our eye out for something better (simpler/better
documented), but nothing firm yet.

The next release of libjingle should have reference code for all of these
layers, and can be used as-is (we do), or as a basis for your own code.

-Bri

On 8/17/06, Lars T. Mikkelsen <ltm at mulm.dk> wrote:
>
> Hi Tobias,
>
> On Thu, Aug 17, 2006 at 01:21:02PM +0200, Tobias Markmann wrote:
> [snip]
> > But since GTalk has no way to see the XML log I don't know how they've
> > implemented that.
>
> If you enable 'diagnostic logging' the Google Talk client will create a
> logfile with XML stanzas sent and received.
>
> Best regards,
> Lars
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.jabber.org/pipermail/standards/attachments/20060817/3ac56da2/attachment.html