Please use this template for reporting suspected bugs or requests for help.
Issue description
I use publisher with zmq_bind and subscriber with zmq_connect. I want subscriber could discover publisher is lost for some errors and reconnect again, so I set ZMQ_HEARTBEAT_IVL, ZMQ_HEARTBEAT_TIMEOUT and ZMQ_HEARTBEAT_TTL for the subscriber socket.
I find the order of calling zmq_setsockopt and zmq_connect will influnce who send ZMTP PING. But I expect the subscriber always sends SMTP PING.
Environment
libzmq version (commit hash if unreleased): v4.3.2
Please use this template for reporting suspected bugs or requests for help.
Issue description
I use publisher with zmq_bind and subscriber with zmq_connect. I want subscriber could discover publisher is lost for some errors and reconnect again, so I set ZMQ_HEARTBEAT_IVL, ZMQ_HEARTBEAT_TIMEOUT and ZMQ_HEARTBEAT_TTL for the subscriber socket.
I find the order of calling zmq_setsockopt and zmq_connect will influnce who send ZMTP PING. But I expect the subscriber always sends SMTP PING.
Environment
Minimal test code / Steps to reproduce the issue
publisher send PING
subscriber send PING