That would break the transport abstraction in 0mq, not all transports are IP based. If you're thinking of using IP addresses as a whitelist/blacklist security mechanism, I would suggest looking at the curve security stuff instead. IP based security is easily defeated.
http://curvezmq.org/ If you're looking to just log connections, you can get that from the OS, for example on Linux: http://gr8idea.info/os/tutorials/security/iptables5.html -Michel On Wed, Jun 11, 2014 at 7:16 PM, 余志昌 <[email protected]> wrote: > Hi Michel, > XPUB looks good. However I want more details info: the SUBs' address > info(IP + TCP port). Is that possible? > Regards, > Zhichang > > > 2014-06-12 9:40 GMT+08:00 Michel Pelletier <[email protected]>: > > Subscriptions are received in the form of incoming messages you get by >> calling recv on the xpub socket. >> >> http://api.zeromq.org/3-2:zmq-socket >> >> "Same as ZMQ_PUB except that you can receive subscriptions from the >> peers in form of incoming messages. Subscription message is a byte 1 (for >> subscriptions) or byte 0 (for unsubscriptions) followed by the subscription >> body." >> >> -Michel >> >> >> On Wed, Jun 11, 2014 at 6:26 PM, 余志昌 <[email protected]> wrote: >> >>> I don't see routines to dump xpub_t::subscriptions. >>> >>> Regards, >>> Zhichang >>> >>> _______________________________________________ >>> zeromq-dev mailing list >>> [email protected] >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >>> >>> >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
