Qore zmq Module
1.0.0
|
Variables | |
const | Qore::ZMQ::ZMQ_BLOCKY = ZMQ_BLOCKY |
Fix blocky behavior. More... | |
const | Qore::ZMQ::ZMQ_IO_THREADS = ZMQ_IO_THREADS |
Set number of I/O threads. More... | |
const | Qore::ZMQ::ZMQ_MAX_MSGSZ = ZMQ_MAX_MSGSZ |
Set maximum message size. More... | |
const | Qore::ZMQ::ZMQ_MAX_SOCKETS = ZMQ_MAX_SOCKETS |
Set maximum number of sockets. More... | |
These constants plus ZMQ_IPV6 define the possible options for the ZContext::setOption() and ZContext::getOption() methods
const Qore::ZMQ::ZMQ_BLOCKY = ZMQ_BLOCKY |
Fix blocky behavior.
When ZMQ_BLOCKY is set to false, all new sockets are given a linger timeout of zero.
By default the context will block indefinitely in the destructor (which calls zmq_ctx_term()
).
The assumption behind this behavior is that abrupt termination will cause message loss. Most real applications use some form of handshaking to ensure applications receive termination messages, and then terminate the context with ZMQ_LINGER set to zero on all sockets. This setting is an easier way to get the same result; when ZMQ_BLOCKY is set to False, all new sockets are given a linger timeout of zero.
You must still close all sockets before deleting the ZContext.
const Qore::ZMQ::ZMQ_IO_THREADS = ZMQ_IO_THREADS |
Set number of I/O threads.
The ZMQ_IO_THREADS argument specifies the size of the ØMQ thread pool to handle I/O operations. If your application is using only the inproc
transport for messaging you may set this to zero, otherwise set it to at least one.
Default value: 1
const Qore::ZMQ::ZMQ_MAX_MSGSZ = ZMQ_MAX_MSGSZ |
Set maximum message size.
Sets the maximum allowed size of a message sent in the context.
Default value: MAXINT
const Qore::ZMQ::ZMQ_MAX_SOCKETS = ZMQ_MAX_SOCKETS |
Set maximum number of sockets.
Sets the maximum number of sockets allowed on the context.
Default value: 1024