[telepathy-gabble/master] Implement send_candidates in Google transport

Will Thompson will.thompson at collabora.co.uk
Sat Jun 27 04:01:00 PDT 2009


gtalk-p2p candidates are never included in session/content actions, only
in transport-infos.
---
 src/jingle-transport-google.c |    9 +++++++--
 1 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/src/jingle-transport-google.c b/src/jingle-transport-google.c
index 3417d94..2d1fea1 100644
--- a/src/jingle-transport-google.c
+++ b/src/jingle-transport-google.c
@@ -553,7 +553,7 @@ new_local_candidates (GabbleJingleTransportIface *obj, GList *new_candidates)
 }
 
 static void
-retransmit_candidates (GabbleJingleTransportIface *obj, gboolean all)
+send_candidates (GabbleJingleTransportIface *obj, gboolean all)
 {
   GabbleJingleTransportGoogle *transport =
     GABBLE_JINGLE_TRANSPORT_GOOGLE (obj);
@@ -599,8 +599,13 @@ transport_iface_init (gpointer g_iface, gpointer iface_data)
   GabbleJingleTransportIfaceClass *klass = (GabbleJingleTransportIfaceClass *) g_iface;
 
   klass->parse_candidates = parse_candidates;
+
   klass->new_local_candidates = new_local_candidates;
-  klass->retransmit_candidates = retransmit_candidates;
+  /* Not implementing inject_candidates: gtalk-p2p candidates are always sent
+   * in transport-info or equivalent.
+   */
+  klass->send_candidates = send_candidates;
+
   klass->get_remote_candidates = get_remote_candidates;
   klass->get_transport_type = get_transport_type;
 }
-- 
1.5.6.5




More information about the telepathy-commits mailing list