Merge remote-tracking branch 'upstream/master' into security
This commit is contained in:
commit
2da100a3c7
35 changed files with 671 additions and 157 deletions
|
@ -95,7 +95,7 @@ will help.</p><p>The default value is: &quot;false&quot;.<
|
|||
<p>This option specifies whether a network socket will be created for
|
||||
each domain participant on a host. The specification seems to assume that
|
||||
each participant has a unique address, and setting this option will
|
||||
ensure this to be the case. This is not the defeault.</p>
|
||||
ensure this to be the case. This is not the default.</p>
|
||||
|
||||
<p>Disabling it slightly improves performance and reduces network traffic
|
||||
somewhat. It also causes the set of port numbers needed by Cyclone DDS to
|
||||
|
@ -712,7 +712,7 @@ d0).</p><p>The default value is: &quot;0&quot;.</p></x
|
|||
<xs:element name="ParticipantGain" type="xs:integer">
|
||||
<xs:annotation>
|
||||
<xs:documentation>
|
||||
<p>This element specifies the participant gain, relating p0, articipant
|
||||
<p>This element specifies the participant gain, relating p0, participant
|
||||
index to sets of port numbers (refer to the DDSI 2.1 specification,
|
||||
section 9.6.1, constant PG).</p><p>The default value is:
|
||||
&quot;2&quot;.</p></xs:documentation>
|
||||
|
@ -1187,8 +1187,8 @@ keys.</p><p>The default value is: &quot;false&quot;.</p&g
|
|||
<xs:element name="HeartbeatInterval">
|
||||
<xs:annotation>
|
||||
<xs:documentation>
|
||||
<p>This elemnents allows configuring the base interval for sending writer
|
||||
heartbeats and the bounds within it can vary.</p>
|
||||
<p>This element allows configuring the base interval for sending writer
|
||||
heartbeats and the bounds within which it can vary.</p>
|
||||
|
||||
<p>Valid values are finite durations with an explicit unit or the keyword
|
||||
'inf' for infinity. Recognised units: ns, us, ms, s, min, hr,
|
||||
|
@ -1725,8 +1725,8 @@ transport. Enabling write batching causes multiple small write operations
|
|||
to be aggregated within the write cache into a single larger write. This
|
||||
gives greater throughput at the expense of latency. Currently there is no
|
||||
mechanism for the write cache to automatically flush itself, so that if
|
||||
write batching is enabled, the application may havee to use the
|
||||
dds_write_flush function to ensure thta all samples are
|
||||
write batching is enabled, the application may have to use the
|
||||
dds_write_flush function to ensure that all samples are
|
||||
written.</p><p>The default value is: &quot;false&quot;.</p></xs:documentation>
|
||||
</xs:annotation>
|
||||
</xs:element>
|
||||
|
@ -2309,8 +2309,8 @@ or Tracing/EnabledCategory settings.</p><p>The default value is:
|
|||
<xs:documentation>
|
||||
<p>This option specifies the file to which received and sent packets will
|
||||
be logged in the "pcap" format suitable for analysis using common
|
||||
networking tools, such as WireShark. IP and UDP headers are ficitious, in
|
||||
particular the destination address of received packets. The TTL may be
|
||||
networking tools, such as WireShark. IP and UDP headers are fictitious,
|
||||
in particular the destination address of received packets. The TTL may be
|
||||
used to distinguish between sent and received packets: it is 255 for sent
|
||||
packets and 128 for received ones. Currently IPv4 only.</p><p>The default
|
||||
value is: &quot;&quot;.</p></xs:documentation>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue