diff options
| author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2013-09-06 12:01:51 +0100 |
|---|---|---|
| committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2013-09-06 15:48:20 +0100 |
| commit | 0ed8a3af94781475354aec323a8e225787f07a48 (patch) | |
| tree | 3d1b5751f565d698e53ea100bc60935fbaf4dbec | |
| parent | 02db7af6e60a69d4e23f3e0c187967cbc5a459bd (diff) | |
| download | telepathy-glib-0ed8a3af94781475354aec323a8e225787f07a48.tar.gz | |
TpConnection: don't recommend that applications call Connect()
For most applications, the rule is "the account manager does that".
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54061
Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
| -rw-r--r-- | telepathy-glib/connection.c | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/telepathy-glib/connection.c b/telepathy-glib/connection.c index 177d1fe82..cc648add1 100644 --- a/telepathy-glib/connection.c +++ b/telepathy-glib/connection.c @@ -144,8 +144,12 @@ tp_connection_get_feature_quark_core (void) * <title>Someone still has to call Connect()</title> * <para>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.</para> + * 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. + * </para> * </note> * * One can ask for a feature to be prepared using the |