[Jingle] Call forking

Peter Saint-Andre stpeter at stpeter.im
Wed Oct 14 21:07:09 CDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/8/09 9:57 PM, Justin Uberti wrote:
> My experience is that in practice, forking is the only comprehensive
> solution. I was against forking for a long time but I really think it is
> what the user expects to happen.
> 
> Our current approach at Google is to identify the most recently active
> capable client and send the call there, but we sometimes we get it
> wrong, perhaps because the user has just left their desk/switched
> browser tabs/etc.
> 
> Calling all endpoints and then sending a terminate message with a
> "cancel" reason to the other endpoints seems like a reasonable approach.

Well this is basically what Google Talk does for messages, too, right?

> Doing ICE in this situation may be very complicated though.

Not necessarily complicated, I think, just an awful lot of packets. :)

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrWg80ACgkQNL8k5A2w/vzcjACfYh5cpc77i5NwGDDmW1GEQXGy
PbsAnifxumZLAbGvzvUwL5yPNCkHzYfv
=J//y
-----END PGP SIGNATURE-----



More information about the Jingle mailing list