[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-285) Subscribe options for retained messages
[ https://issues.oasis-open.org/browse/MQTT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62920#comment-62920 ] Andrew Banks commented on MQTT-285: ----------------------------------- There is an opportunity here to modify the "SHOULD store the new QoS 0 messages" statement and make this behaviour mandatory. The NoSendRetain flag needs to send new retained messages but not previously sent ones. It effectively means ignore the new subscription if a previous one exists. > Subscribe options for retained messages > --------------------------------------- > > Key: MQTT-285 > URL: https://issues.oasis-open.org/browse/MQTT-285 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: New Feature > Components: futures > Affects Versions: 5 > Reporter: Ken Borgendale > Assignee: Ken Borgendale > > This issue came up when reviewing MQTT-235 (nolocal) as it affects the bridge use case along with others. > The current setting of the retain flag on PUBLISH and the handling of retained messages on SUBSCRIBE is normally correct when the client really is a subscribing client, it is not correct behavior when the client is going to forward the message on in a bridge or filter use case. > There are two issues here > 1. In some case the subscriber does not want to get any messages which are retained at the time of the subscription. > 2. If the subscriber is going to re-publish the message it needs to know if the messages was published with the retain flag, rather than that it came from a retained source -- 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]