Re: [amqp-comment] amqp over http draft

[Gordon Sim <gsim@redhat.com>]

On 24/05/2019 7:30 pm, Clemens Vasters wrote:
> the subject contains the HTTP status or request line, with the URI
> field of the request line already broken out into “to”. It is a 
> straight mapping, no munging.

No, it is not.

Your prefixes 'http:req' and 'http:rsp' do not occur in either the 
request-line or status-line.

The HTTP request-line is method, uri and version. The uri is mapped to 
the to field, as you say, and there is an http:version application 
property defined. The draft text says the method goes in the subject but 
is prefixed (it does *not* say that the request-line minus the URI goes 
in the subject)

The HTTP status-line is version, code and reason. Again the version and 
reason have application-properties defined for them and the draft text 
states the code goes in the subject but is prefixed.

HTTP uses a simple text based encoding with space separated elements in 
the request-line and status-line. AMQP has a rich type system that 
obviates the need for munging together different fields in a string with 
special separators.

If the subject contained the method or status-code *without* munging in 
the special prefixes, it *would* be a straight mapping. Straight and 
clean. All the information from the request-line and status-line would 
be preserved and sensibly represented in the AMQP message.