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. Thanks for your response. Paul ________________________________________ From: Rob Godfrey [rob.j.godf...@gmail.com] Sent: Tuesday, March 01, 2016 9:43 AM To: users@qpid.apache.org Subject: Re: General Question: QPID Implementation of AMQP Type Notation Hi Paul, I'm not sure I completely understand your question. Section 1.3 is describing the notation within the specification itself used to define types - i.e. it is telling you how to read the XML files which make up the specification. It's not really meaningful to talk about the Qpid components "supporting" the notation. What is it that you are looking to do / for Qpid to support? -- Rob On 1 March 2016 at 16:35, Flores, Paul A. <paul.a.flo...@saic.com> wrote: > Just a very general question. > > > > How does QPID support the Type Notation as described in Section 1.3 of > AMQP OASIS standard? > > > > To what degree is it supported at this time? > > > > Thanks. > > > > Paul > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
