[zeromq-dev] need malamute API to query clients

[Kenneth Adam Miller]

Well one shortcut you could use in malamute that would get you off the
ground immediately is to alter the endpoint routes for each of the
respective groups so that you can interject a process chain. In this way,
you can delegate the management of those clients by having malamute reflect
that information on to a second intermediary. So, group A sends to endpoint
X, group B sends to endpoint Y. Malamute switches all of X and Y over to a
process, which does some upkeep and forwards that information on to the
opposite side for the respective origin. It would impose some message
latency, but hey it's an quick way to get started and have it do what you
want, and when you get done or malamute has that feature added, you can
work with that and just change a couple of names in your original source.

On Wed, Jul 22, 2015 at 10:00 AM, Pieter Hintjens <ph at imatix.com> wrote:

> This is a good idea. The broker needs an admin protocol (this is a
> common problem in brokers). One option is to build that protocol on
> top of Malamute, so e.g. talk to a system service, or subscribe to a
> system stream...
>
> On Wed, Jul 22, 2015 at 3:05 PM, Miao Lin <miaolin71 at gmail.com> wrote:
> > Hi:
> >      I think malamute should add api like mlm_get_clients to list all
> > clients connected, and also have such stream like SYSTEM that broad
> client
> > connect/disconnect msg.
> >
> >      of course can write a client to do this, but since all client
> > connections are stored in malamute server, if expose api, should be
> better?
> >
> > Best
> > Miao
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150722/2d46fdce/attachment.htm>