mirror of
https://github.com/zeromq/libzmq.git
synced 2025-01-31 14:39:55 +01:00
Fixed (un)signed type errors in get/setsockopt manual
This commit is contained in:
parent
a12f446c4c
commit
e74d350068
@ -60,7 +60,7 @@ type.
|
||||
The default 'ZMQ_HWM' value of zero means "no limit".
|
||||
|
||||
[horizontal]
|
||||
Option value type:: int64_t
|
||||
Option value type:: uint64_t
|
||||
Option value unit:: messages
|
||||
Default value:: 0
|
||||
Applicable socket types:: all
|
||||
@ -99,7 +99,7 @@ See also linkzmq:zmq_init[3] for details on allocating the number of I/O
|
||||
threads for a specific _context_.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: int64_t
|
||||
Option value type:: uint64_t
|
||||
Option value unit:: N/A (bitmap)
|
||||
Default value:: 0
|
||||
Applicable socket types:: N/A
|
||||
@ -134,7 +134,7 @@ The 'ZMQ_RATE' option shall retrieve the maximum send or receive data rate for
|
||||
multicast transports using the specified 'socket'.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: kilobits per second
|
||||
Default value:: 100
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
@ -148,7 +148,7 @@ determines the maximum time in seconds that a receiver can be absent from a
|
||||
multicast group before unrecoverable data loss will occur.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: seconds
|
||||
Default value:: 10
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
@ -165,7 +165,7 @@ on performance. Where possible, disable 'ZMQ_MCAST_LOOP' in production
|
||||
environments.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: boolean
|
||||
Default value:: 1
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
|
@ -39,7 +39,7 @@ type.
|
||||
The default 'ZMQ_HWM' value of zero means "no limit".
|
||||
|
||||
[horizontal]
|
||||
Option value type:: int64_t
|
||||
Option value type:: uint64_t
|
||||
Option value unit:: messages
|
||||
Default value:: 0
|
||||
Applicable socket types:: all
|
||||
@ -78,7 +78,7 @@ See also linkzmq:zmq_init[3] for details on allocating the number of I/O
|
||||
threads for a specific _context_.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: int64_t
|
||||
Option value type:: uint64_t
|
||||
Option value unit:: N/A (bitmap)
|
||||
Default value:: 0
|
||||
Applicable socket types:: N/A
|
||||
@ -147,7 +147,7 @@ The 'ZMQ_RATE' option shall set the maximum send or receive data rate for
|
||||
multicast transports such as linkzmq:zmq_pgm[7] using the specified 'socket'.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: kilobits per second
|
||||
Default value:: 100
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
@ -165,7 +165,7 @@ needed for recovery will be held in memory. For example, a 1 minute recovery
|
||||
interval at a data rate of 1Gbps requires a 7GB in-memory buffer.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: seconds
|
||||
Default value:: 10
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
@ -182,7 +182,7 @@ performance. Where possible, disable 'ZMQ_MCAST_LOOP' in production
|
||||
environments.
|
||||
|
||||
[horizontal]
|
||||
Option value type:: uint64_t
|
||||
Option value type:: int64_t
|
||||
Option value unit:: boolean
|
||||
Default value:: 1
|
||||
Applicable socket types:: all, when using multicast transports
|
||||
|
Loading…
x
Reference in New Issue
Block a user