Re: [amqp-comment] amqp over http draft

[Gordon Sim <gsim@redhat.com>]

On 24/05/2019 8:13 am, Clemens Vasters wrote:
> The projected mode is specifically designed to preserve HTTP semantics 
> at the request-level, and if I have an endpoint that accepts HTTP 
> requests but then also accepts other messages, I need to distinguish the 
> two kinds of messages.

Why? At the point you are accepting HTTP you know it is HTTP. At the 
point you are handling the AMQP message, the details of that messages 
should be sufficient. It has the target address, any headers, the method 
etc and can be converted back to HTTP if needed by the ultimate recipient.

> Polluting the application-properties is not optimal, because that’s 
> where all the HTTP headers go that aren’t otherwise explicitly mapped 
> and since we aim to be transparent, I can’t really reserve a name in 
> that section.

To me it is not necessary in the application-properties either, but is 
is much less optimal to have it as a prefix in the subject where it 
infects every AMQP application involved. That will really limit the 
appeal of this spec.

What about defining a message-annotation that you can add if you want to 
know the protocol that caused the generation of the message?