Bindings should probably just ignore deprecated options unless there's an explicit reason to support them.
On Fri, Jan 9, 2015 at 10:31 AM, Arnaud Kapp <kapp.a...@gmail.com> wrote: > I'd say write that it is deprecated. > One should use the ZAP API as it's more flexible and allows for more > configuration. > > As soon as the ZAP API is available, encourage your user to use it > over other means of filtering / securing connection. > > At least that's my opinion. > > On Thu, Jan 8, 2015 at 3:35 PM, Peter Kleiweg <pklei...@xs4all.nl> wrote: >> >> The API doc version 4.1 for setsockopt option >> ZMQ_TCP_ACCEPT_FILTER says this option is deprecated, and you >> should use the ZAP API instead. >> >> The API doc version 4.0 doesn't say this, but the ZAP API is >> already available. >> >> Writing bindings for ZeroMQ 4, should I write in the docs that >> this option is deprecated since 4.1, or should I just write that >> it is deprecated? >> >> >> -- >> Peter Kleiweg >> http://pkleiweg.home.xs4all.nl/ >> _______________________________________________ >> zeromq-dev mailing list >> zeromq-dev@lists.zeromq.org >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > -- > Kapp Arnaud - Xaqq > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
