On 01/29/2013 07:48 PM, Fraser Adams wrote:
When I said "ObjectMessage is the only way to expose amqp/map and amqp/list" I did caveat that with "and properly conform to the spec. " :-)
I think that approach deviates from the spec in a similar sort of subtle way the use of MapMessage does, i.e. you can't send any Serializable object in the map or list.
I do accept it provides quite a nice and consistent interface provided you can explicitly control the encoding to use when sending.
I'm not violently opposed to "Being able to treat it as some other message type may also be reasonable. " and I know from our conversations wrt. Proton that you've got some views with respect to providing choice. That's kind of fair, though my *personal* view is that it's ultimately a good idea to provide consistency and encourage common design patterns.
Yes, choice can be good but it can sometimes by unnecessary and confusing. In this particular case my view is that if an application is able to handle one of the message types and you could expose the data to them in a way that makes sense, why not do so.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
