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-345) re connection and re transmission

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

Brian Raymor commented on MQTT-345:

And there's also:

1018 with a long Session Expiry, if they intend to re connect to the Server at some later point in time.

1023 This Client can use a short Session Expiry so that it can re connect when the network is available
1024 again and continue reliable message delivery. If the Client does not re connect, allowing the

1027 If the Client connects using this protocol, then re connects using the MQTT V3.1.1 protocol using

2308 The server is not obliged to use the same set of subscription identifiers in a re transmitted

2311 transmission in any re transmission. Alternatively the Server is allowed to use the new identifiers in a re
2312 transmission. The Server is not allowed to revert to the old identifier if it has

> re connection and re transmission
> ---------------------------------
>                 Key: MQTT-345
>                 URL: https://issues.oasis-open.org/browse/MQTT-345
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Trivial
>             Fix For: 5, wd10
> 975 After re connection the Session lasts as long as the Network Connection plus the new Session Expiry
> 976 interval.

This message was sent by Atlassian JIRA

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