[zeromq-dev] How to write a malamute to malamute bridge?
Miao Lin
miaolin71 at gmail.com
Mon Oct 26 13:17:26 CET 2015
For standard application, publish to one stream is reasonable, but for a
malamute to malamtue bridge, especially in a malamute cluster, re-publish
all msg from one malamute to another means a lot of streams, if re-publish
each stream through one connection, that means tones of connections between
malamute, it is not reasonable, right?
if I using a star topology, as more and more servers and applitions join
the cluster, these connections will become nightmare? say if I have n
servers working on m streams, there will have n*m connection to the center
server?
Best
Miao
2015-10-24 18:44 GMT+08:00 Miao Lin <miaolin71 at gmail.com>:
> "It's a problem I'm thinking of working on... you could do this
> manually by consuming from one broker and republishing to another."
>
>
> It is what I am doing. but problem is , when I republishing message to another, I must use a bunch of producer, each producer can only publish message to one stream, I want to know if is possible to use only one producer publish to many stream?
>
>
> Thank you .
>
> best
>
> Miao
>
>
> 2015-10-23 20:47 GMT+08:00 Miao Lin <miaolin71 at gmail.com>:
>
>> Hi:
>> I am trying to build a small malamute cluster, suppose to write a
>> bridge app connect to 2 malamute instances, copy message from one malamute
>> to another and visa verse.
>>
>> problem is , I can listen to all streams through one listener, but I
>> can not send message to different streams via one connection, in malamute
>> api, seems I have to bind the connection to a certain stream before send
>> message.
>>
>> That means I have to use a lot of connections to send message, each
>> connection for only one stream.
>> Are there any idea to send to arbitrary stream only with one producer
>> connection?
>>
>> Thanks.
>>
>> Miao Lin
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20151026/2d748582/attachment.htm>
More information about the zeromq-dev
mailing list