Re: [amqp-comment] amqp over http draft

[Gordon Sim <gsim@redhat.com>]

On 28/05/2019 2:42 pm, Clemens Vasters wrote:
> Scenario:
> a) one set of paired links forming a bi-directional channel
> b) an HTTP service at each end, forming a "dialog" or "callback" interface.
> c) the services have an ongoing bi-directional conversation, each acting towards the other as client. That's not at all outlandish in IoT.
> d) the "client" service also sends telemetry events multiplexed with requests
>
> Here, I need to triage HTTP requests and HTTP responses at the endpoints to the right correlators and then handlers and also have messages that are one-way telemetry data that I want to dispatch elsewhere.

Would the 'to' field not be a good way to indicate different 'targets'? 
I.e. requests and telemetry would use different addresses and responses 
would of course use the reply-to address from the request they are in 
answer to.