[zeromq-dev] API break in 4.1.x

Arnaud Kapp kapp.arno at gmail.com
Sat Oct 25 23:21:25 CEST 2014

Hi Pieter,

I am currently using this feature. I realize that this
can be worked around by manually looking up a hashmap with the socket
identity as a key.
I am not sure if there is such a workaround if someone is monitoring a 
STREAM socket.

I'd suggest making this a configurable option instead of removing it.

On 10/25/2014 09:08 PM, Pieter Hintjens wrote:
> Hi all,
> We've noticed this commit broke the API in 4.1.x:
> mmit afb24b53e6d1fc39cd1b73be706b335ed5c7b6fb
> Author: Goswin von Brederlow <goswin-v-b at web.de>
> Date:   Fri Jan 17 23:21:42 2014 +0100
>      Add STREAM connect notification.
>      Adjust test cases to connection notification.
>      Increase error checking in test cases.
> This change breaks existing applications. Does anyone have an
> objection to either removing it, or making it a configurable socket
> option?
> -Pieter
> Ps. also, volunteers to clean this up?  :-)
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list