[Telepathy-commits] [telepathy-glib/master] ChannelFactoryIface: explain how and why it is deprecated.

Will Thompson will.thompson at collabora.co.uk
Mon Sep 15 10:05:38 PDT 2008


---
 telepathy-glib/channel-factory-iface.c |   13 ++++++-------
 1 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/telepathy-glib/channel-factory-iface.c b/telepathy-glib/channel-factory-iface.c
index 31c6e8d..e2dcde6 100644
--- a/telepathy-glib/channel-factory-iface.c
+++ b/telepathy-glib/channel-factory-iface.c
@@ -34,13 +34,12 @@
  * all requests and all incoming events, but in general, there will be
  * multiple channel factories handling different types of channel.
  *
- * For example, at the time of writing, Gabble has a roster channel factory
- * which handles contact lists and groups, an IM channel factory which
- * handles one-to-one messaging, a MUC channel factory which handles
- * multi-user chat rooms and the index of chat rooms, and a media channel
- * factory which handles VoIP calls.
- *
- * @deprecated since 0.7.UNRELEASED; use #TpChannelManager instead.
+ * @deprecated since 0.7.UNRELEASED. #TpChannelManager is a newer interface for
+ *             allocating and tracking channels which supports the Requests
+ *             D-Bus interface introduced in version 0.17.11 of the
+ *             specification.  New connection managers should implement that
+ *             interface instead, and existing connection managers should
+ *             migrate to it.
  */
 
 #include <telepathy-glib/channel-factory-iface.h>
-- 
1.5.6.5




More information about the Telepathy-commits mailing list