[Bug 29451] Too many asynchronous setup steps needed for basic usage

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29451

--- Comment #11 from Olli Salli <ollisal at gmail.com> 2010-08-18 07:12:24 PDT ---
I've inspected the requestAndHandle situation, and the tp-glib model of
exporting a temporary Client with no filters seems like the approach to take.
It will fit in with the semantics I suggested - there is no application-visible
Client object (well, a relevant one anyway) so the only place to specify
features will be the AM which the Account belongs to, which IS most logical
indeed. However, this brings up another issue - should it be supported to
"start" from an Tp::Account without getting it either from an AM or a Client?
If it should, there won't be any means to specify the desired connection
features.

A possible solution:
 - keep the Account and Connection factories separate
 - have just the ConnectionFactory in Account
 - have AM specify its own ConnectionFactory for all sub-accounts

Then again, is this needed? AFAICS all apps DO either use AM or get a single
account/connection at a time given to them when observing/handling/approving.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.