Bug 53596 - random division of responsibility between YtsClient and YtsRoster
Summary: random division of responsibility between YtsClient and YtsRoster
Status: NEW
Alias: None
Product: Ytstenut
Classification: Unclassified
Component: ytstenut-glib (show other bugs)
Version: unspecified
Hardware: Other All
: low enhancement
Assignee: ytstenut
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-16 15:48 UTC by Simon McVittie
Modified: 2012-08-17 11:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2012-08-16 15:48:06 UTC 
YtsClient and YtsRoster have a 1:1 relationship. The public API would be simpler if YtsRoster was an implementation detail, and all of its public API moved to YtsClient.
Comment 1 Robert Staudinger 2012-08-17 11:00:54 UTC 
To provide some perspective, I think the original idea was that if an app only provides services, you just need the YtsClient. If you want to discover and use services, you use the roster.

The plans for refactoring were that the Roster was instantiated by the application only when needed, and registered with the Client, so it could be kept up to date.

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.