[Bug 24906] GSM-compatible conference calls

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=24906





--- Comment #17 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2009-12-01 09:09:24 PST ---
Arguments against Merge being in Conference:

* it's another mandatory-to-implement vtable slot for CMs

* in protocols where the CM really just falls back to inviting the target
handle, the API is lying

* it makes the desired API for text clients harder to explain: "you upgrade
channels like *this* (you can also Merge(), but ignore that)"

* in practice, UIs are more likely to want to invite people than they are to
want to merge channels (Empathy's current invitation UI is merge-like, which
isn't discoverable enough - people keep asking in #empathy "why can't I invite
people?", followed eventually by "oh, *that's* how you do it")

Arguments for Merge being in Conference:

* clients that prefer to Merge (if there are any? possibly only Call clients,
not Text?) need to look at whether the interface is present

16:55 * sjoerd dislikes having a new interface for one method that has a 
        completely obvious fallback path in protcools that don't support it

Relatedly:

16:58 < sjoerd> smcv: btw does the MergableBadgers interface have a way of 
                saying you can't merge more channels in ?
16:58 < smcv> sjoerd: no. it could, if you want it to
16:58 < smcv> sjoerd: I don't know what protocol could support that, though
16:59 < smcv> sjoerd: in XMPP it's unlimited, in GSM I think it's unlimited 
              until the network tells you you can't?
16:59 < sjoerd> Not sure if say GSM has a limit on how many people you can 
                merge into a conference
16:59 * sjoerd was just idly wondering about stuff


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.