Bug 27364

Summary:	Account.I.Conditions implementation
Product:	Telepathy	Reporter:	Simon McVittie <smcv>
Component:	mission-control	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	mardy, sjoerd
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	24896
Bug Blocks:	24762

Description Simon McVittie 2010-03-29 05:02:43 UTC

Cloned from Bug #24762, which said:

"""
At the moment MC has a very large plugin API, which we can't keep stable for very long at a time due to internal refactoring; as a result, we've turned off plugin support in Debian and recommend that all distributions do the same. This is basically rubbish.

...

Subsequent things to do to close this bug:

...

* work out how to turn the connectivity API (as used in Maemo 5) into a plugin too
"""

The current connectivity API is not directly suitable, since it splits the logic between MC and the plugin, with a number of subtle interactions; this is hard to maintain.

Comment 1 Will Thompson 2010-06-03 07:56:23 UTC

Rob and I discussed this a bit the other day. Accounts could have a property — provided by the account storage backend, so it can be fixed for Ring — specifying whether the account should always be online, should be online whenever we have a wireless connection, or online when we have any connection. Then MC would track how connected we are (using ConnMan, Network Manager, ConIc, etc. as appropriate) and semi-disable accounts accordingly.

Comment 2 Alberto Mardegan 2010-06-03 11:35:41 UTC

The logic should be a bit more flexible: consider tp-salut for instance, which could be online even when a wireless connection was established without a route.
Or another interesting case is VPN: some company network (often sip-based) might be available only when a specific VPN is active.

Comment 3 Simon McVittie 2014-01-30 13:26:31 UTC

This is WONTFIX until someone designs the API. There seems no point in having two bugs track this, and the spec one has more discussion, so I'm closing this.

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

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.