RE: [amqp-comment] amqp over http draft

[Clemens Vasters <clemensv@microsoft.com>]

Thank you, Gordon.

We had the same debate about the subject field content at the F2F meeting. The reason for the prefix is that we also need to know whether it's a 'http' request to which this spec applies vs. any other message sent to the same endpoint. I wanted to avoid using an application-property for that. It's surely debatable whether we need the second indicator for request and response or whether we can infer that from the presence of reply-to/correlation-id, but while we already have the 'http' prefix, I'm not sure that's simpler. 

Question is: How do I clearly flag a message as an http message inside the bare message without having to pollute the application-properties section?

I agree on lowercase conversion. We should indeed leave the method as-is. 

Clemens 

-----Original Message-----
From: Gordon Sim <gsim@redhat.com> 
Sent: Thursday, May 23, 2019 11:54 PM
To: amqp-comment@lists.oasis-open.org
Subject: [amqp-comment] amqp over http draft

The http:req: and http:rsp: prefixes the http-over-amqp spec draft requires on the subject are ugly and inefficient. They are also unnecessary.

The subject is a status-code for a response which must be a three digit string and although the http spec does not prohibit a three digit method extension I think that possibility can be safely ignored. The presence of reply-to would also indicate a request, and the presence of correlation-id a response.

The method should also *not* be converted to lowercase. Http methods are case sensitive.

Amqp clients and services can then use the familiar methods and status codes regardless of whether the client or service for any interaction is actually using http and bridging where it occurs does not require unnecessary string manipulation.

For once, please err on the side of simplicity!

--Gordon.



--
This publicly archived list offers a means to provide input to the OASIS Advanced Message Queuing Protocol (AMQP) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: amqp-comment-subscribe@lists.oasis-open.org
Unsubscribe: amqp-comment-unsubscribe@lists.oasis-open.org
List help: amqp-comment-help@lists.oasis-open.org
List archive: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.oasis-open.org%2Farchives%2Famqp-comment%2F&amp;data=02%7C01%7Cclemensv%40microsoft.com%7C6e8e13b7871d48be954c08d6dfc92421%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636942452322674729&amp;sdata=LwoeT2W6dsHJUl%2BbpxrgKW2s91D7lxxRprH12WIAoL0%3D&amp;reserved=0
Feedback License: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oasis-open.org%2Fwho%2Fipr%2Ffeedback_license.pdf&amp;data=02%7C01%7Cclemensv%40microsoft.com%7C6e8e13b7871d48be954c08d6dfc92421%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636942452322674729&amp;sdata=AEw%2BGoFwtP2bQ2%2FM0xOqqSEIDu1pmB8LW55XEtmEPxs%3D&amp;reserved=0
List Guidelines: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oasis-open.org%2Fmaillists%2Fguidelines.php&amp;data=02%7C01%7Cclemensv%40microsoft.com%7C6e8e13b7871d48be954c08d6dfc92421%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636942452322674729&amp;sdata=WlYAu7Ps8TJr0ISOA07D1eIWNEehp850ur8Xf9VPhHE%3D&amp;reserved=0
Committee: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Famqp&amp;data=02%7C01%7Cclemensv%40microsoft.com%7C6e8e13b7871d48be954c08d6dfc92421%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636942452322674729&amp;sdata=s6aLgphUeEouyJkMI%2Fb0biVbboJttaU23%2BaWdk%2Fz92g%3D&amp;reserved=0
Join OASIS: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oasis-open.org%2Fjoin%2F&amp;data=02%7C01%7Cclemensv%40microsoft.com%7C6e8e13b7871d48be954c08d6dfc92421%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636942452322674729&amp;sdata=1jVFVIaSbOJoXWQyLs2sTk9QvG74Hn5jenWoMZR58Dg%3D&amp;reserved=0