falconair wrote:
If the callback method returns IMessage itself, then the user has to get
application headers out of it, then get at the actual attributes. That
looks unintuitive to me since the attributes of message are the most
important piece of the message.
According to me a message has a body and some properties or headers;
Note that this is the case with JMS.
Bypassing IMessage completely also doesn't
make sense since it does contain useful information. Perhaps somehow making
IMessage a type of dictionary directly (rather than making
ApplicationHeaders a member of IMessage) will do the trick?
I don't think we should change IMessage as it represents an AMQP
message. We can however, and I thought this is what you were after ,
introduce a wrapper around IMessage that would hide the AMQP
specificities. This wrapper could be if you wish a Dictionary that may
provide access to the message body through a specific key. What do you
think?
Arnaud
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
