[Telepathy-commits] [telepathy-glib/master] Requests: clarify chaining of functions
Will Thompson
will.thompson at collabora.co.uk
Mon Sep 15 09:01:06 PDT 2008
---
telepathy-glib/base-connection.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/telepathy-glib/base-connection.c b/telepathy-glib/base-connection.c
index 08e8616..fa18dc0 100644
--- a/telepathy-glib/base-connection.c
+++ b/telepathy-glib/base-connection.c
@@ -2436,7 +2436,10 @@ service_iface_init (gpointer g_iface, gpointer iface_data)
}
-/* Prototypes for stages of requestotron */
+/* The handling of calls to Connection.Interface.Requests.CreateChannel is
+ * split into three chained functions, which each call the next function in
+ * the chain unless an error has occured.
+ */
static void conn_requests_check_basic_properties (TpBaseConnection *self,
GHashTable *requested_properties, ChannelRequestMethod method,
DBusGMethodInvocation *context);
@@ -2470,6 +2473,9 @@ conn_requests_requestotron (TpBaseConnection *self,
{
TP_BASE_CONNECTION_ERROR_IF_NOT_CONNECTED (self, context);
+ /* Call the first function in the chain handling incoming requests; it will
+ * call the next steps.
+ */
conn_requests_check_basic_properties (self, requested_properties, method,
context);
}
--
1.5.6.5
More information about the Telepathy-commits
mailing list