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-299) Metadata: CONNECT and CONNACK Maximum Message Length

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

Konstantin Dotchkoff commented on MQTT-299:

Discarding a message would solve the challenge, however the client will never receive messages w/o even knowing they've been discarded. 
If the Server sends a DISCONNECT, the Client most likely will try to reconnect and SUBSCRIBE again to receive the same message. This might lead to a cycle of a client trying to reconnect and receive messages, and the larger message would be like a poison message.
Could we consider to have max message size on the Topic and Clients that cannot handle that size would fail to subscribe to the topic. (e.g. the max message size is specified on subscribe instead of on connect). The challenge though is how the max. message size for a topic can be specified - especially in the case Client subscribe, before anyone has published to a Topic. Any thoughts on this?

> Metadata: CONNECT and CONNACK Maximum Message Length
> ----------------------------------------------------
>                 Key: MQTT-299
>                 URL: https://issues.oasis-open.org/browse/MQTT-299
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5
>            Reporter: Brian Raymor
>            Assignee: Ed Briggs
> This was discussed in MQTT-276 (with notes from the F2F meetings) and has been tracked in MQTT-256 (Metadata). 
> I'm opening a separate, specific issue per Ken's comments - https://issues.oasis-open.org/browse/MQTT-256?focusedCommentId=62192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-62192:
> "All of these would be defined in separate JIRAs, but what we should do in this JIRA is to define the mechanism used to pass these values."

This message was sent by Atlassian JIRA

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