I think we should remove everyone in such situation. 'unsubscribe' is a conscious decision compared to a disconnect which could happen even due to a network outage. Thoughts?
On Mon, Aug 31, 2015 at 11:02 AM, Pamod Sylvester <pa...@wso2.com> wrote: > Hi All, > > When enabled shared subscriptions, it creates subscription groups which > are distinguished through the client ids of the consumers. hence, for a > given durable topic it allows multiple subscriptions to be bound with the > same client id, in return when a message is delivered, for the consumers > bound with the same client id, the messages will be load balanced. > > The question is, > > in the event where one of the subscriptions with a given client id sends > an unsubscribe request, > > 1) should we remove all the other subscriptions bound to the topic with > the same client id or > 2) should we remove only that particular subscription ? > > To elaborate more, the following is an example, > > i.e let's say there're 10 subscriptions with the same client id bound to a > topic as shared durable subscriptions, if the 10th subscriber sends a > un-subscription request should we remove all other 9 subscriptions > belonging to the group or should we remove only that particular > subscription and eventually remove the underlaying queue which persists > offline messages when we identify when the request is sent by the last > subscription belonging to the shared subscription group (client id). > > What should be the best way to handle this ? > > Thanks, > Pamod > -- > *Pamod Sylvester * > > *WSO2 Inc.; http://wso2.com <http://wso2.com>* > cell: +94 77 7779495 > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
