[zeromq-dev] Monitoring and management question

Pieter Hintjens ph at imatix.com
Mon Dec 27 20:14:43 CET 2010


Why not simply post a warning in the manual that using this information for
business logic is severely disrecommended. You cannot really 'lock down'
functionality, and abuse is other a relative point of view.

It would be more useful imo to open up the data in a usable for and clearly
explain WHY using it for higher level decisions is inaccurate and fragile,
than either not exposing the data, or obfuscating it in some way.

Assume our users are mostly not idiots...

On 23 Dec 2010 09:32, "Martin Sustrik" <sustrik at 250bpm.com> wrote:
> On 12/23/2010 12:47 AM, Paul Colomiets wrote:
>> Or even maybe socket type, which could look like:
>> sock = ctx.socket(zmq.MONITOR)
>> sock.bind('inproc://connections')
>> realsock = ctx.socket(zmq.REQ)
>> realsock.connect('inproc://connections')
>> realsock.send("active")
>> print realsock.recv()
> Yes. It's done that way. The only difference is that you use zmq.SUB
> instead of zmq.MONITOR and "sys://log" instead of "inproc://connections".
>> This way monitoring capabilities can be directly exposed to the
>> monitoring software on the network.
>> This way you will make improper usage of this information more hard.
> It's not particularly hard. I mean, as hard as to prevent unappropriate
> usage.
> What would do would be reporting is such a format that it can't be
> parsed by a machine, say "There are three hundred and twenty three
> connections and seven thousand five hundred and seven messages queued
> altogether." with some randomisation in the word order and spelling as
> to confuse parsers.
> Not really a neat solution :)
> Martin
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101227/667b8483/attachment.htm>

More information about the zeromq-dev mailing list