[zeromq-dev] Feature requests/thoughts for TCP transport

Sergey Hripchenko shripchenko at intermedia.net
Tue Apr 3 12:55:42 CEST 2012

The guides you provided suggests me to fork against zeromq/libzmq.
But the code in ' libzmq' somewhat changed from 'zeromq2-1' which I currently use.
How these changes will be backported to 2.1 code? (of course if they fully backward compatible)
Or I should provide patches against zmq2.1?

I'm just talking about new setsockopt(ZMQ_*) mentioned earlier

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Pieter Hintjens
Sent: Tuesday, April 03, 2012 1:47 AM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] Feature requests/thoughts for TCP transport

Hi Sergey,

Our contribution policy is here:
http://www.zeromq.org/docs:contributing. More broadly we're aiming at http://rfc.zeromq.org/spec:16.

You'll have more success presenting changes as answers to specific problems, rather than "features".

And yes, we accept pull requests (whereas we don't record feature requests).


> 1.        zmq->socket(*)->setsockopt(ZMQ_TCP_KEEPALIVE) on both
> (server and
> client) ends for fault tolerant connections:

Difficult to do, would probably affect the protocol. But people would definitely like it.

> 2.        zmq->socket(*)->setsockopt(ZMQ_TCP_MAX_PEERS, int) before 3.
> zmq->socket(*)->setsockopt(ZMQ_TCP_MAX_PEERS_BY_IP, int) before 4.
> multiple zmq->socket(*)->setsockopt(ZMQ_TCP_ACCEPT_FROM, cidr)

All highly valuable.

> 5.        zmq->socket(*)->setsockopt(ZMQ_TCP_AUTH_TOKEN, string) on
> server and client sides for peer authentication…. This is though… it
> breaks protocol compatibility…

Difficult to do, and breaks the protocol. You would need to find ways of adding versioning to the protocol first.

> 6.        zmq->socket(*)->disconnect(tcp://connstring) as  the
> opposite to
> zmq->socket(*)->connect(tcp://connstring)

Valuable, relatively easy to do.

zeromq-dev mailing list
zeromq-dev at lists.zeromq.org


This message is intended only for the person(s) to which it is addressed and may contain Intermedia.net Inc privileged, confidential and/or proprietary information. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Any disclosure, copying, distribution, or the taking of any action concerning the contents of this message and any attachment(s) by anyone other than the named recipient(s) is strictly prohibited.

More information about the zeromq-dev mailing list