[zeromq-dev] getsockopt/setsockopt

Brian Granger ellisonbg at gmail.com
Wed Apr 28 19:56:30 CEST 2010


On Tue, Apr 27, 2010 at 11:09 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> Brian Granger wrote:
>> Hi,
>> I am adding support for the new multipart messages in the Python
>> bindings and as part of this I am wrapping getsockopt.
>> I have a few questions about what options it makes sense to call
>> getsockopt for.  More specifically, the string valued
>> options are presenting problems for getsockopt:
>> zmq.IDENTITY:  Get Invalid argument error upon getsockopt.  Segfault
>> if IDENTITY has not been setsockopt'd
> Aha. Looks like a bug.

OK, I will file a bug report on this.

>> zmq.SUBSCRIBE/UNSUBSCRIBE:  Get Invalid argument error upon getsockopt.
>> Do these even make sense to call getsockopt on?
> No. It doesn't make sense.

OK great, I will exclude these.



> Martin

Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu
ellisonbg at gmail.com

More information about the zeromq-dev mailing list