On Wed, 2017-11-01 at 12:10 +0000, Gordon Sim wrote: > On 01/11/17 10:16, Lorenz Quack wrote: > > > > For global subscription on the other hand the client uses a random > > UUID associated with the connection as its own container-id. This > > means that on every new connection a new link is being estblished > > rather than recovering an existing one. Over time these subscription > > links would accumulate on the broker until the subscription is > > unsubscribed. > I may of be misunderstanding the issue, but my understanding was that > the portion of the link name after (and including) the '|', should be > ignored in identifying the shared terminus. > > There would be no need to store and link specific information for a link > from such a global, shared subscription once a link is no longer active. >
Hi Gordon, What about link specific state like the unsettled map? To me it seems we would need to preserve that. On a side note, in the broker-j implementation the termini are actually not shared. This means that you can, for example, use different filters on different subscribers of a shared subscription. Kind regards, Lorenz --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
