amqp over http draft

[Gordon Sim <gsim@redhat.com>]

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.