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

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

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

Shawn McAllister commented on MQTT-274:
---------------------------------------

This jira addresses sections of the WD that deal with requirements and need to add this feature to MQTTv5. Subsequent discussions have happened and then again at the WG meeting on Sept 8 where we agreed to move forward with this feature - so this question has been resolved. Appropriate text to support this feature will be transferred to the v5 specification and this does not typically include requirements and justification.

As a result, I believe there are no issues left to resolve with this jira so I am closing it.

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