[zeromq-dev] subscribe/unsubscribe refcounting behaviour

[Pieter Hintjens]

On Tue, Aug 17, 2010 at 11:28 PM, Jon Dyte <jon at totient.co.uk> wrote:

> This means that the client has to keep track of how many subscriptions
> it has issued in order to cancel it.
> 1) is everyone aware of this?
> 2) are they happy with it?

Aware of it, and not happy with it.  Basically and with all respect to
the authors, it looks like an API that documents code behavior, not
code that implements a designed API.

I've just posted a lengthy proposal for a new SUB API.  I should have,
but forgot to, cover this particular issue.  Setting prefix criteria
should be idempotent (i.e. if done again, have no further effect).

You can do a workaround which is to explicitly UNSUBSCRIBE before
every SUBSCRIBE but apps should not have to do this.

-Pieter