DOCS, Streaming: Clarified situations with batch (un)subscriptions

s-kostyuk · May 6, 2018 · 028d5b1 · 028d5b1
1 parent f3600bb
commit 028d5b1
Showing 1 changed file with 16 additions and 5 deletions.
diff --git a/docs/source/api/streaming_api.rst b/docs/source/api/streaming_api.rst
@@ -214,7 +214,7 @@ following message:
         "timestamp": 123456.76,
         "topic": "stream/subscribe",
         "body": {
-            "target_topic": "here/is/your/topic".
+            "target_topic": "here/is/your/topic",
             "messages_retained": 0
         }
     }
@@ -233,14 +233,21 @@ Where:
 In response to that message you will receive the following message
 with an empty body:
 
+In response to that message you will receive the following message:
+
 .. code-block:: json
 
     {
         "timestamp": 123456.76,
         "topic": "stream/subscribe_ack",
-        "body": {}
+        "body": {
+            "target_topic": "here/is/your/topic"
+        }
     }
 
+Where ``target_topic`` is the same topic that was specified in
+the ``subscribe`` message.
+
 
 Wildcard subscriptions
 ^^^^^^^^^^^^^^^^^^^^^^
@@ -297,17 +304,21 @@ Where:
   (``here/is/your/topic`` on example).
 
 
-In response to that message you will receive the following message
-with an empty body:
+In response to that message you will receive the following message:
 
 .. code-block:: json
 
     {
         "timestamp": 123456.76,
         "topic": "stream/unsubscribe_ack",
-        "body": {}
+        "body": {
+            "target_topic": "here/is/your/topic"
+        }
     }
 
+Where ``target_topic`` is the same topic that was specified in
+the ``unsubscribe`` message.
+
 
 Authentication
 --------------