Bug 20906

Summary:	[MC5] Account.UpdateParameters violates telepathy-spec
Product:	Telepathy	Reporter:	Simon McVittie <smcv>
Component:	mission-control	Assignee:	Simon McVittie <smcv>
Status:	RESOLVED DUPLICATE	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Simon McVittie 2009-03-27 07:07:29 UTC

+++ This bug was initially created as a clone of Bug #20905 +++

Mission Control 5 disconnects and reconnects the account whenever properties that are not a DBusProperty are changed, in violation of telepathy-spec. This is in order to achieve an "instant apply" model. However, I believe that MC is the wrong place for this policy enforcement.

Possible solutions for MC 5's use case:

* Change the spec to document MC 5's behaviour, overruling my objection

* (API break) make UpdateParameters return a boolean, "reconnect required", and let the client do the reconnect when it wants to - consider adding a Reconnect method too. libmcclient's method to update parameters could be patched to call Reconnect whenever necessary, keeping its C API unchanged

* Add a new parameter-updating method paralleling UpdateParameters that has one of the above behaviours

Discuss.

Comment 1 Simon McVittie 2009-04-14 07:25:14 UTC


*** This bug has been marked as a duplicate of bug 21154 ***

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.