[OASIS Issue Tracker] (MQTT-274) Request-Response needs clarity on what is supportable in MQTT 3.1.1

From
OASIS Issues Tracker <>
Date
2016-09-02T21:56:15+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-274) Request-Response needs clarity on what is supportable in MQTT 3.1.1
[ https://issues.oasis-open.org/browse/MQTT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Raymor updated MQTT-274:
------------------------------

    Affects Version/s: 5
                           (was: 3.1.1)

> Request-Response needs clarity on what is supportable in MQTT 3.1.1
> -------------------------------------------------------------------
>
>                 Key: MQTT-274
>                 URL: https://issues.oasis-open.org/browse/MQTT-274
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: ReqRespMEP
>    Affects Versions: 5
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Shawn McAllister
>
> WD01 shows a use case (client networking configuration), but then discusses a strawman (HTTP). Pub/Sub with correlation can be used to do the Request/Response pattern, not precisely in the manner anticipated, but functionally useful.
> A description of why typical patterns such as private topic use for request/response do not work should be included.
> The document does not convince that there's a real problem that needs solution with a change to the MQTT 3.1.1 specification.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)