[OASIS Issue Tracker] (MQTT-235) NoLocal Subscription for MQTT Subscribers

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61548#comment-61548 ] 

Ken Borgendale commented on MQTT-235:
-------------------------------------

When we consider nolocal support, we should also consider this relative to other issues.  While nolocal is pretty simple in the simple server case, it is more complicated in the complex server case and should be considered relative to MQTT-276.  It also must be defined in any implementation of shared subscriptions and should be considered as part of MQTT-234.

As for other bridge requirements, the other one (besides nolocal and retain as published) is to not send retained messages on re-subscribe.  Like the others, this is useful for things other than bridge. 

> NoLocal Subscription for MQTT Subscribers 
> ------------------------------------------
>
>                 Key: MQTT-235
>                 URL: https://issues.oasis-open.org/browse/MQTT-235
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Rahul Gupta
>            Priority: Critical
>             Fix For: 3.1.1
>
>
> Based on a query in MQTT Google group, a query was posted with a requirement that the server should not publish message to a subscriber if messages are published by the same client-id and subscribed by the using the same client-id for the same topic. In this case a client connection may both publish and subscribe to a topic and the subscriber should inhibit the delivery of messages published by its own connection. This feature is available in JMS and a subscriber can inhibit to receive publication by using the noLocal flag during subscription.
> This feature is also needed to enable bridging and making proxy subscription between servers so as to stop messages going round in loops.
> I would like propose to add a element in SUBSCRIBE Control packet for individual subscriptions to make a choice on noLocal parameter.  This field could be shared in the same byte as for requstedQos. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)