summaryrefslogtreecommitdiff
path: root/gisi
diff options
context:
space:
mode:
authorAki Niemi <aki.niemi@nokia.com>2010-05-14 16:44:48 +0300
committerAki Niemi <aki.niemi@nokia.com>2010-05-14 16:51:30 +0300
commit9ac5c596ed0e462099882f55a8b439499e956369 (patch)
tree49ed2d8402e28834eb7fda3a9c1473ef23c63c48 /gisi
parent36bd9985974e16844b67e08d9813b803c5eeb725 (diff)
downloadofono-9ac5c596ed0e462099882f55a8b439499e956369.tar.gz
gisi: Add support for NTF requests
Notify requests are requests sent by ISA servers towards clients. They are identical to indications in that no response is necessary, but different in that subscription is done not using the mechanism used for indications, but out-of-band. Typically routing for notify requests is enabled using a request-response pair.
Diffstat (limited to 'gisi')
-rw-r--r--gisi/client.c7
1 files changed, 6 insertions, 1 deletions
diff --git a/gisi/client.c b/gisi/client.c
index e5af0644..fa40f0c7 100644
--- a/gisi/client.c
+++ b/gisi/client.c
@@ -560,8 +560,13 @@ static void g_isi_dispatch_response(GIsiClient *client, uint16_t obj,
unsigned id = msg[0];
ret = tfind(&id, &client->reqs.pending, g_isi_cmp);
- if (!ret)
+ if (!ret) {
+ /* This could either be an unsolicited response, which
+ * we will ignore, or an incoming request, which we
+ * handle just like an incoming indication */
+ g_isi_dispatch_indication(client, obj, msg + 1, len - 1);
return;
+ }
req = *(GIsiRequest **)ret;