[OASIS Issue Tracker] (MQTT-217) Deliver implementation guidance around overlapping subscriptions

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

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

Andrew Banks commented on MQTT-217:
-----------------------------------

MQTT253 (add subscription ids) tried to address this but was abandoned. Other ways to address this, might be: 

- Require that a server that sends multiple messages should mark all but the first message as repeat a message. 
- A server should announce on CONNACK that it is going to send multiple responses when needed. 
- The server should add a unique identifier to a publish message so that the client can eliminate the repeat messages 
  if it needs to.

> Deliver implementation guidance around overlapping subscriptions
> ----------------------------------------------------------------
>
>                 Key: MQTT-217
>                 URL: https://issues.oasis-open.org/browse/MQTT-217
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 5
>            Reporter: Richard Coppen
>            Priority: Minor
>
> Following on from David Kemper's mqtt-comment on CSPRD02 the TC agreed to open this Jira to deliver implementation guidance around overlapping subscriptions.



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