[OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/MQTT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-14:
-------------------------------

    Component/s: core
                     (was: edits)

moved to core

> Tighten up language in Quality of Service levels and flows 
> -----------------------------------------------------------
>
>                 Key: MQTT-14
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-14
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Rahul Gupta
>            Assignee: Rahul Gupta
>            Priority: Minor
>
> It was today reported in MQTT google group. https://mail.google.com/mail/?shva=1#inbox/13ec114a841305d9
> ----------
> The spec explains (http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html#qos-flows) that when a message is published to the server with qos 1 the server should persist it, deliver it to all subscribers, delete the message and then puback.
> Does this require the server to wait for puback from all subscribers which subscribed with qos1 before sending puback to the original publisher? What about disconnected qos1 subscribers, are they exempted?
> My concern is that the pub/puback takes a whole lot longer in this case, without any extra reliability benefits. Couldn't the server send puback as soon as the message is persisted? 
> ----------
> Language in specification needs to be tightened up

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