Type of socket to create
Implicit ZeroMQ application context
Bitmask defining the socket's I/O thread affinity.
Maximum number of queued outstanding connections.
Bind the socket to a local endpoint.
Bind the socket to a local endpoint.
URL-like specification of local address
Close the socket.
Close the socket. This is also called automatically when the object is finalized. The socket becomes unusable after the first successful call to this method, but it doesn't hurt to call the method again.
Connect the socket to a remote endpoint.
Connect the socket to a remote endpoint.
URL-like specification of remote address.
Implicit ZeroMQ application context
Current polling state of the socket.
A file descriptor that can be polled to check the status of this socket.
The native handle for the socket.
Whether the send and receive methods should process routing information prepended to payload message parts.
Whether the send and receive methods should process routing information prepended to payload message parts. This is true by default for router sockets, false for all other socket types.
Whether the send and receive methods should add or remove an empty separator between the routing and payload message parts.
Whether the send and receive methods should add or remove an empty separator between the routing and payload message parts. This is false by default but should be enabled for routers communicating with requestors or responders.
Hard limit on the maximum number of outstanding messages queued in memory.
Application specific socket identifier.
Linger period for socket shutdown, as a time value with unit.
Linger period for socket shutdown, as a time value with unit. Negative values are allowed and mean infinity.
Maximum reconnection interval for lost connections, as a time value with unit.
Whether data sent in a multicast transmission can be received by the sender, too.
Pipeline of transformations that are applied to outgoing and incoming messages.
Pipeline of transformations that are applied to outgoing and incoming messages. The pipeline stages are applied from left to right when sending a message and from right to left when receiving a message.
Maximum data rate for multicast transmissions, in kilobits per second.
Receive a message through the transport.
Receive a message through the transport.
Whether the operation should block (default: true)
The incoming message and its routing path
Kernel transmission buffer size when receiving.
Reconnection interval for lost connections, as a time value with unit.
Send a message through the transport.
Send a message through the transport.
Whether the operation should block (default: true)
Kernel transmission buffer size when sending.
The socket underlying this transport.
The socket underlying this transport.
Effective socket type.
Subscribe to messages with a given prefix.
Subscribe to messages with a given prefix.
Buffer whose contents from start to limit form the prefix
Size of disk buffers for outstanding messages that exceed the high water mark of the in-memory queue.
Perform a non-blocking receive operation and report the blocking error condition through an empty return value.
Perform a non-blocking receive operation and report the blocking error condition through an empty return value.
Some message if the receive was successful, none if it would block
Perform a non-blocking send operation and report the blocking error condition through a boolean return value.
Perform a non-blocking send operation and report the blocking error condition through a boolean return value.
The message to transmit
Routing path for the message
true if the send was successful, false if it would block
Unsubscribe to messages with a given prefix.
Unsubscribe to messages with a given prefix.
Buffer whose contents from start to limit form the prefix
ZeroMQ socket. This class is not thread-safe, just like its underlying native backend.