epics/pvAccess
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

pipeLine: specify option ackAny

Browse Source
This commit is contained in:
mrkraimer
2015-12-10 13:45:37 -05:00
parent 7c8dc748fe
commit cf2e4a9b4c
1 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
documentation/pvAccessCPP.html
View File

@ -1439,11 +1439,20 @@ where
This is implemented by allowing the client to make the server delay when the client can not keep up with the server.
</p>
<p>The server implememts Channel::createMonitor but none of the other create methods.
When the client creates a monitor the following request options must be specified:</p>
When the client creates a monitor the following request options can be specified:</p>
<pre>
"record[queueSize=size,pipeline=true]"
"record[pipeline=true,queueSize=size,ackAny=n]"
</pre>
<p>Each time the client calls <b>Monitor::release</b> the client sends an <b>ack</b> message to the server.
where
<dl>
<dt>pipeline</dt>
<dd>This option must be set true.</dd>
<dt>queueSize</dt>
<dd>This option is optional.</dd>
<dt>ackAny</dt>
<dd>This option is optional. If not specified the value is queueSize/2.</dd>
</dl>
<p>Each time the client calls <b>Monitor::release</b> the client sends an <b>ack</b> message to the server every <b>ackAny</b> events.
The server uses this to delay sending new monitors if the monitor queue is full.</p>
<p><b>pvAccessCPP/testApp/remote/pipelineServiceExample.cpp</b> Is an example.</p>
<h3>pipelineServer</h3>