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=60733#comment-60733 ] 

Ken Borgendale commented on MQTT-274:

It is certainly possible to do req/resp within MQTT v3.1.1 with the understanding that it is a private convention between the requesting and responding clients.  Applications do this all of the time.

Therefore the real requirement here is to elevate this from private conventions to a public one which allows either complex servers to correctly handle the routing, or for the request and response to be routed outside of MQTT by the servers. 

There is also an implied requirements here for usability in that it should be easier for the clients to use this function than rolling their own, and that defining this in the spec will foster more use of this sort of messaging.  These really need to be the explicit requirements as without them the case for adding this to the spec is smaller.

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