OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (MQTT-478) What does "remade a subscription" mean?


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

Ken Borgendale commented on MQTT-478:
-------------------------------------

Is the concern the use of the word "remade" or the concept of the paragraph?  It is not clear to me that recreated or resubscribed are different from remade (but then, any would seem to be acceptable).

The concept is that if you change subIDs for a subscription while the server is retransmitting messages, the two are asynchronous and that the subscribe completes does not guarantee that subsequent messages received will have the new subID.  I do not think the paragraph as it exists is wrong.

> What does "remade a subscription" mean?
> ---------------------------------------
>
>                 Key: MQTT-478
>                 URL: https://issues.oasis-open.org/browse/MQTT-478
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd14
>            Reporter: Konstantin Dotchkoff
>            Priority: Minor
>             Fix For: 5, wd14
>
>
> This issue was originally reported in MQTT-417, but doesn't seem to be addressed in WD14. 
> Lines 2498-2499
> "If the Client remade a subscription after the initial transmission of a PUBLISH packet ..."
> "remade" – does that mean resubscribed or maybe recreated? According to [MQTT-3.8.4-3] this would replace the current subscription, even if it has a new identifier. This means the old identifier wouldn’t be valid anymore. The paragraph is a bit confusing, so I’m not sure what we mean by remade and how a subscription might end up having 2 identifiers (an old and a new one). 



--
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]