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-253) Subscription identification


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

Andrew Banks edited comment on MQTT-253 at 11/17/16 6:46 AM:
-------------------------------------------------------------

Added by mistake, intended for issue 320


was (Author: andrew_banks):
Ed, the worst consequences of inaccurate clocks that you mention seem to be:
1) A client mail fail to send PINREQ in time.
    The client could mitigate this by asking for a longer keep alive interval or by accepting that it will have to reconnect. Another possibility would be for the Client to not use Keep alive and rely on a server initiate ping to detect liveness.
   

2) A server might expire state sooner than it should.

This would happen if the server clock drifts or is corrected towards the future. The server might know this could happen, for example because it is using a of day clock which is reporting
a time before some hard coded value which is clearly wrong ,  like 15 November 2016 (its 17 November at the time of writing) . In this case it could be very lenient with its expiry and perhaps never expire the data.


> Subscription identification
> ---------------------------
>
>                 Key: MQTT-253
>                 URL: https://issues.oasis-open.org/browse/MQTT-253
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 5
>            Reporter: Andrew Schofield
>            Assignee: Andrew Banks
>            Priority: Minor
>
> Subscribe and unsubscribe operations are performed on topic filters in MQTT 3.1.1. Adding subscription identifiers would enable unambiguous identification of subscriptions.



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