On Tue, 2016-03-01 at 22:13 +0000, Flores, Paul A. wrote: > Hi Rob, > > The question came about during a discussion if there was a way to > configure a broker such that queues would have specifically > structured messages. In that scenario a client or application could > query a broker to obtain a queue specific message format or perhaps > have the broker reject or segregate messages that were incorrectly > formatted. > > Apparently section 1.3 of the standard (Type Notations) "fueled" the > speculation a bit. After a more thorough read thru, more "moderated" > enthusiasm and substantial coffee the question has morphed into a > discussion of how we can standardize message format specification and > creation.
Possibly useful info: You can use the AMQP type system to format message bodies. There isn't a general notation for it but all the qpid-proton language bindings will convert between an AMQP-formatted payload and some language equivalent types like arrays, maps, lists etc. AMQP messages have a standard content-type field that you can set/examine to check the message encoding before you try to unpack the message. If you have some other serialization format you like, you are free to use that. The AMQP encoding is provided for convenience with the proton clients (and might be supported by other AMQP clients) but otherwise there's nothing magical about it. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
