[zeromq-dev] [PATCH] Publisher side filtering

Gerard Toonstra gtoonstra at gmail.com
Wed Jan 19 11:43:08 CET 2011


I'm testing this from the sub-forward branch.  Following are some
preliminary results and I'm trying to find the cause of the last one:

   - I'm using a broker, which forwards messages from sub->pub for sub
   changes and pub->sub as usual.
   - I'm using wireshark to investigate the sub update traffic
   - Broker is started, pub is started, then sub is started, the sub change
   is forwarded upstream to pub. So the typical use-case works when connections
   are established.
   - When pub is restarted, it continues to work, but this is because the
   pub is not actively filtering messages. It just sends every message to the
   broker. The pub does not show a message "subscription received" on a
   restart, indicating the broker does not actively forward known subscriptions
   when it is reconnected (same issue as below).
   - When sub is restarted, it sends the subscription every time, so this is
   the way to reestablish the message path.

What does not work yet:

   - When broker is killed and then restarted, the sub is temporarily
   disconnected, but no "xattach_pipes" is being called in xsub_t, so no
   subscriptions are sent upstream after broker crash. This patch I believe,
   was meant to catch disconnects in the session and then call xattach_pipes
   again when the tcp connection was reinstated?



On Fri, Jan 14, 2011 at 5:54 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> Gerard,
> Finally, here's the patch that should trigger subscriptions to be re-sent
> when socket re-connects to a particular peer. However, this patch wasn't
> tested yet.
> Martin

Gerard Toonstra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110119/465154e4/attachment.htm>

More information about the zeromq-dev mailing list