[Telepathy-commits] [telepathy-qt4/master] DBusProxy: note what would be needed for feature parity with TpProxy

Simon McVittie simon.mcvittie at collabora.co.uk
Wed Jan 14 04:55:26 PST 2009


---
 TelepathyQt4/Client/dbus-proxy.cpp |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/TelepathyQt4/Client/dbus-proxy.cpp b/TelepathyQt4/Client/dbus-proxy.cpp
index 0200393..3f2caa0 100644
--- a/TelepathyQt4/Client/dbus-proxy.cpp
+++ b/TelepathyQt4/Client/dbus-proxy.cpp
@@ -37,6 +37,14 @@ namespace Client
 
 // ==== DBusProxy ======================================================
 
+// Features in TpProxy but not here:
+// * tracking which interfaces we have (in tpqt4, subclasses do that)
+// * being Introspectable, a Peer and a Properties implementation
+// * disconnecting from signals when invalidated (probably has to be in the
+//   generated code)
+// * making methods always raise an error when called after invalidated
+//   (has to be in the generated code)
+
 class DBusProxy::Private
 {
 public:
-- 
1.5.6.5




More information about the Telepathy-commits mailing list