OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [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:comment-tabpanel&focusedCommentId=60734#comment-60734 ] 

Shawn McAllister commented on MQTT-274:

These are good points, Ken.  There is also the key point that while applications can develop private conventions for request/reply, it is much less likely (close to zero) that these conventions will be interoperable for apps/products developed independently (who therefore choose different conventions).  Standard or public conventions are required to enable interoperability between such applications - and such interoperability is the primary mandate of MQTT as a standard protocol.

I will make these points in the document, but perhaps they should be more part of the motivation for creating this feature vs specific technical requirements of the feature?

> 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
>         Environment: William Cox
>            Reporter: William Cox
> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]