request/response over pub/sub
Making publish/subscribe behave like ask-and-answer by publishing a request and waiting for a reply on another topic.
Request/response over pub/sub publishes a request with a correlation ID and a response topic, then waits, with a timeout, for a reply carrying the same correlation ID.
Examples
To ask a bench node to blink, the app subscribes to
gh1/<device-id>/cmd/res, publishes the request tocmd/reqat QoS 1, and gives up if no matching reply arrives within about five seconds.
See also