[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-68) Message delivery retry is not required where no network failure is detected
[ http://tools.oasis-open.org/issues/browse/MQTT-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34308#action_34308 ] Raphael Cohen commented on MQTT-68: ----------------------------------- I've always thought this was more of a problem when a connection is re-established after network failure - were the first thing a client should do is retry delivery of failed stuff. I've never been too clear if that include SUBSCRIBE and UNSUBSCRIBE... > Message delivery retry is not required where no network failure is detected > ---------------------------------------------------------------------------- > > Key: MQTT-68 > URL: http://tools.oasis-open.org/issues/browse/MQTT-68 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Affects Versions: 3.1.1 > Reporter: Richard Coppen > Fix For: 3.1.1 > > > WD08 (section 4.3) states that if no response is received from PUBLISH, PUBREL, SUBSCRIBE, UNSUBSCRIBE within a reasonable period of time then the sender may retry delivery. > This attempts to cater for unreliable TCP/IP networks. Since modern compliant TCP/IP networks should not lose packets, then the sender should not retry unless a network failure is detected. > The spec should be changed to reflect this and add non-normative content to describe the historical problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]