| Summary: | random division of responsibility between YtsClient and YtsRoster | ||
|---|---|---|---|
| Product: | Ytstenut | Reporter: | Simon McVittie <smcv> |
| Component: | ytstenut-glib | Assignee: | ytstenut |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | low | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Simon McVittie
2012-08-16 15:48:06 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.