[Telepathy-commits] [telepathy-spec/master] AccountManager: recommend that "the" AM is not service-activatable

[Simon McVittie]

This would bring up various issues with choosing between alternative
implementations (if both Mission Control and Decibel implement AccountManager,
which one should be service-activated for the AccountManager well-known name?)
so instead we let (UIs launched by) the desktop session decide which one to
use.
---
 spec/Account_Manager.xml |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/spec/Account_Manager.xml b/spec/Account_Manager.xml
index a068da3..6c5c12b 100644
--- a/spec/Account_Manager.xml
+++ b/spec/Account_Manager.xml
@@ -29,6 +29,15 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
         the session bus. This process must export an
         /org/freedesktop/Telepathy/AccountManager object with the
         AccountManager interface.</p>
+
+      <p>Until a mechanism exists for making a reasonable automatic choice
+        of AccountManager implementation, it is RECOMMENDED that
+        implementations do not register as an activatable service for the
+        AccountManager's well-known bus name. Instead, it is intended that
+        some component of the user's session will select and activate a
+        particular implementation, and that other Telepathy-enabled programs
+        can detect whether Telepathy is in use by checking whether the
+        AccountManager's well-known name is in use at runtime.</p>
     </tp:docstring>
     <tp:added version="0.17.2"/>
 
-- 
1.5.6.3