Bug 32021 - TpAccountManager should always ensure TP_ACCOUNT_FEATURE_CORE is prepared
Summary: TpAccountManager should always ensure TP_ACCOUNT_FEATURE_CORE is prepared
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/wj...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2010-12-01 08:53 UTC by Will Thompson
Modified: 2010-12-07 07:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2010-12-01 08:53:56 UTC 
Currently, TP_ACCOUNT_MANAGER_FEATURE_CORE becoming ready means that TP_ACCOUNT_FEATURE_CORE is prepared on all the accounts that existed at the time that TP_ACCOUNT_MANAGER_FEATURE_CORE was prepared, but no later accounts have this guarantee.

This strikes me as inauspicious. It makes the API harder to use. Happily this isn't currently a problem for me.

The attached branch documents the current behaviour, but doesn't fix this bug. It does also add tp_account_get_path_suffix().
Comment 1 Simon McVittie 2010-12-01 09:00:26 UTC 
(In reply to comment #0)
> The attached branch documents the current behaviour, but doesn't fix this bug.

Clone it, or leave this bug open?

> It does also add tp_account_get_path_suffix().

Looks good: I think it also be worth saying:

    For persistent identification of the account, use
    tp_proxy_get_object_path().

since that's not trivially obvious (due to living in a superclass).

r+ apart from that.
Comment 2 Will Thompson 2010-12-07 07:25:43 UTC 
Fixed and merged.

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.