aboutsummaryrefslogtreecommitdiffstats
path: root/protocol.html
diff options
context:
space:
mode:
authorjason2015-11-23 20:30:11 -0700
committerjason2015-11-23 20:30:11 -0700
commitd04b9708d570bb227aeff7725af8ebbf15dac3e1 (patch)
treead5630f35d6c5d29072b738009d0acee6edc9453 /protocol.html
parent24e99bd13b6d10301484556107841de8ba8ac9e0 (diff)
downloadeventmq-d04b9708d570bb227aeff7725af8ebbf15dac3e1.tar.gz
eventmq-d04b9708d570bb227aeff7725af8ebbf15dac3e1.zip
updates
Diffstat (limited to 'protocol.html')
-rw-r--r--protocol.html36
1 files changed, 36 insertions, 0 deletions
diff --git a/protocol.html b/protocol.html
index ae55ced..9c0994b 100644
--- a/protocol.html
+++ b/protocol.html
@@ -91,6 +91,7 @@
91<li class="toctree-l3"><a class="reference internal" href="#architecture">Architecture</a><ul> 91<li class="toctree-l3"><a class="reference internal" href="#architecture">Architecture</a><ul>
92<li class="toctree-l4"><a class="reference internal" href="#topology">Topology</a></li> 92<li class="toctree-l4"><a class="reference internal" href="#topology">Topology</a></li>
93<li class="toctree-l4"><a class="reference internal" href="#router-addressing">ROUTER Addressing</a></li> 93<li class="toctree-l4"><a class="reference internal" href="#router-addressing">ROUTER Addressing</a></li>
94<li class="toctree-l4"><a class="reference internal" href="#global-frames">Global Frames</a></li>
94<li class="toctree-l4"><a class="reference internal" href="#emqp-client">eMQP / Client</a></li> 95<li class="toctree-l4"><a class="reference internal" href="#emqp-client">eMQP / Client</a></li>
95<li class="toctree-l4"><a class="reference internal" href="#emqp-worker">eMQP / Worker</a></li> 96<li class="toctree-l4"><a class="reference internal" href="#emqp-worker">eMQP / Worker</a></li>
96<li class="toctree-l4"><a class="reference internal" href="#heartbeating">Heartbeating</a></li> 97<li class="toctree-l4"><a class="reference internal" href="#heartbeating">Heartbeating</a></li>
@@ -190,6 +191,41 @@
190&gt; When receiving messages a ROUTER socket shall prepend a message part containing the identity of the originating peer to the message before passing it to the application. When sending messages a ROUTER socket shall remove the first part of the message and use it to determine the identity of the peer the message shall be routed to.</p> 191&gt; When receiving messages a ROUTER socket shall prepend a message part containing the identity of the originating peer to the message before passing it to the application. When sending messages a ROUTER socket shall remove the first part of the message and use it to determine the identity of the peer the message shall be routed to.</p>
191<p>This extra frame is not shown in the specifications below.</p> 192<p>This extra frame is not shown in the specifications below.</p>
192</div> 193</div>
194<div class="section" id="global-frames">
195<h3>Global Frames<a class="headerlink" href="#global-frames" title="Permalink to this headline">¶</a></h3>
196<p>An <strong>ACK</strong> command consists of a 4-frame multipart message, formatted as follows.</p>
197<table border="1" class="docutils">
198<colgroup>
199<col width="14%" />
200<col width="33%" />
201<col width="53%" />
202</colgroup>
203<thead valign="bottom">
204<tr class="row-odd"><th class="head">FRAME</th>
205<th class="head">Value</th>
206<th class="head">Description</th>
207</tr>
208</thead>
209<tbody valign="top">
210<tr class="row-even"><td>0</td>
211<td>_EMPTY_</td>
212<td>leave empty</td>
213</tr>
214<tr class="row-odd"><td>1</td>
215<td>eMQP/1.0</td>
216<td>Protocol version</td>
217</tr>
218<tr class="row-even"><td>2</td>
219<td>ACK</td>
220<td>command</td>
221</tr>
222<tr class="row-odd"><td>3</td>
223<td>_MSGID_</td>
224<td>A unique id for the msg</td>
225</tr>
226</tbody>
227</table>
228</div>
193<div class="section" id="emqp-client"> 229<div class="section" id="emqp-client">
194<h3>eMQP / Client<a class="headerlink" href="#emqp-client" title="Permalink to this headline">¶</a></h3> 230<h3>eMQP / Client<a class="headerlink" href="#emqp-client" title="Permalink to this headline">¶</a></h3>
195<p>A <strong>REQUEST</strong> command consists of a 7-frame multipart message, formatted as follows.</p> 231<p>A <strong>REQUEST</strong> command consists of a 7-frame multipart message, formatted as follows.</p>