Bug 23154

Summary: Connection.Interface.Requests: duplicate onto Connection
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-specAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED INVALID QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Simon McVittie 2009-08-05 07:57:07 UTC 
The functionality of Requests should be a core part of Connection.

Proposed migration path:

* add CreateChannel, Channels etc. to Connection with the same signatures and semantics as in Requests

* augment TpBaseConnection and the Python equivalent to implement both sets of D-Bus API

* when those changes are old enough to rely on, change MC (and any clients that go behind its back) to use the core Connection interface instead of Requests

* deprecate the methods and properties of the Requests interface (to avoid emitting three sets of signals, it's probably OK to not move the signals)

* in Telepathy 1.0 (Bug #23148), delete the Requests interface and move its signals to the core Connection

* when telepathy-glib API is broken, remove TpChannelFactoryIface and all code needed to support it
Comment 1 Simon McVittie 2010-12-01 03:00:20 UTC 
Telepathy 1.0 is relatively imminent and won't be backwards-compatible anyway, and porting will be straightforward, so let's just merge these interfaces at that point.

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.