Bug 22200 - Do we really have to send transport-accept immediately for gtalk4?
Summary: Do we really have to send transport-accept immediately for gtalk4?
Status: RESOLVED NOTABUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: low minor
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 03:44 UTC by Will Thompson
Modified: 2009-06-23 09:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2009-06-10 03:44:29 UTC 
In jingle/incoming-basics.py, I added the following comment:

 # With gtalk4, apparently we have to send transport-accept immediately,
 # not even just before we send our transport-info.
 # FIXME: wjt thinks this is suspicious. It matches the Gabble
 #        implementation, so he moved it here to avoid the test being
 #        racy, but we should do some more interop testing.

It's probably harmless, but I don't know if we actually need it. Maybe we could try removing it and seeing if calling gtalk4 clients still works.

More generally, it'd be good to actually document the quirks of the various Jingle dialects.
Comment 1 Will Thompson 2009-06-23 09:54:21 UTC 
I just tested this, and indeed if Gabble doesn't send transport-accept, incoming calls don't work.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.