Olivier Crête wrote: > See: > http://git.collabora.co.uk/?p=user/sjoerd/telepathy-spec.git;a=commitdiff;h=3b6c5e271660017cc751bdf4cd3fc46003b613f0
See also http://people.freedesktop.org/~sjoerd/telepathy-spec-new_media_spec/spec/ for the human-readable version. >> In Jingle, if Alice and Bob call each other at the same time, the call >> with the lower session ID is meant to win. How do we represent this in >> Telepathy? On the "losing" side, does the call that lost vanish, and >> the new call pop up, or does the existing call silently morph into the >> incoming one? Will thinks the desired user experience is that Alice >> and Bob both click call, and then they're on a call with no further >> interaction. > > The UI should deal with this. Merging concurrent calls in the CM seems > like asking for problems. In particular, for Jabber, the controlling > mode is set according to who started the call. So Farsight needs to be > restarted anyway. Good answer. Okay, I guess the UI needs to deal. But Gabble should close the channel that loses. >> Content names: sometimes they're useful (your Jingle client might >> helpfully call the projector stream "projector") and sometimes they're >> not (your Jingle client might call it "video2"). No real way to >> tell. Maybe Jingle should support extra information: <projector/>, >> <webcam/>, etc. But we should expose the name we do have, so if the >> client wants to apply some heuristic it can. > > Do we supply a way for clients to name their Contents ? Yup: <http://people.freedesktop.org/~sjoerd/telepathy-spec-new_media_spec/spec/org.freedesktop.Telepathy.Channel.Type.Call.Draft.html#org.freedesktop.Telepathy.Channel.Type.Call.Draft.AddContent> -- Will
signature.asc
Description: OpenPGP digital signature
_______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
