[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-235) NoLocal Subscription for MQTT Subscribers
[ https://issues.oasis-open.org/browse/MQTT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63610#comment-63610 ] Jonathan Levell commented on MQTT-235: -------------------------------------- Apologies for my sloppy language in the previous comment. TC agreed that if nolocal was requested on a shared subscription it MUST result in an error being returned on the subscribe. > 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: core > Affects Versions: 5 > Reporter: Rahul Gupta > Assignee: Ken Borgendale > Priority: Critical > Fix For: 5 > > > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]