← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (MQTT-156) Vague treatment of "at most once"

From
OASIS Issues Tracker <>
Date
2014-03-05T16:58:02+00:00
ID
1587547200.16221394038751391.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Commented: (MQTT-156) Vague treatment of "at most once"
[ http://tools.oasis-open.org/issues/browse/MQTT-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36734#action_36734 ] 

Richard Coppen commented on MQTT-156:
-------------------------------------

Looks like a dup of MQTT-102

> Vague treatment of "at most once"
> ---------------------------------
>
>                 Key: MQTT-156
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-156
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Technical
>            Reporter: Patrick Durusau
>
> In 4.3.1 4.3.1 QoS 0: At most once delivery:
> "The message arrives at the receiver either once or not at all."
> At most once delivery raises expectations about making sure no message is delivered twice.
> It is unclear how duplicates of a messages are prevented from "arriving". What mechanism allows for that QoS aspect? (i.e. duplicate elimination). If there is no explicit provision for eliminating duplicates, aren't we rather talking of more simply "Best effort" semantics?

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →