[zeromq-dev] API break in 4.1.x

Pieter Hintjens ph at imatix.com
Sun Oct 26 08:09:19 CET 2014


OK, the functionality is valid and solves a real problem. However what
it creates is an API break that people are treating (correctly) as a
bug: https://gist.github.com/Asmod4n/b843dd3754a98b95e52c

Changing functionality that's been in a stable release isn't allowed.

On Sun, Oct 26, 2014 at 1:36 AM, KIU Shueng Chuan <nixchuan at gmail.com> wrote:
> http://lists.zeromq.org/pipermail/zeromq-dev/2014-April/025977.html
>
> See referred thread. Without the reconnection notification, it would not be
> possible to receive and assemble large messages from the server.
>
> On 26 Oct 2014 03:09, "Pieter Hintjens" <ph at imatix.com> 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
>
>
> _______________________________________________
> 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