From 774687a0e2b690e674fe746eccf0eed02f08e5b9 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Fri, 6 Sep 2013 12:01:51 +0100 Subject: [PATCH 14/19] TpConnection: don't recommend that applications call Connect() For most applications, the rule is "the account manager does that". --- telepathy-glib/connection.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/telepathy-glib/connection.c b/telepathy-glib/connection.c index 177d1fe..cc648ad 100644 --- a/telepathy-glib/connection.c +++ b/telepathy-glib/connection.c @@ -144,8 +144,12 @@ tp_connection_get_feature_quark_core (void) * Someone still has to call Connect() * Requesting this feature via tp_proxy_prepare_async() means that * you want to wait for the connection to connect, but it doesn't actually - * start the process of connecting: to do that, call - * tp_cli_connection_call_connect() separately. + * start the process of connecting. For connections associated with + * a #TpAccount, the account manager service is responsible for + * doing that, but if you are constructing connections directly + * (e.g. if you are implementing an account manager), you must + * tp_cli_connection_call_connect() separately. + * * * * One can ask for a feature to be prepared using the -- 1.8.4.rc3