Damn phone Comparabilty = compatibility
Sent from my Samsung Galaxy smartphone. -------- Original message --------From: "michael.andre.pearce" <michael.andre.pea...@me.com> Date: 25/05/2018 22:59 (GMT+00:00) To: dev@activemq.apache.org Subject: Re: Custom serialization mechanism for ActiveMQMessages So our one in our org is avro. This is about enabling users to choose their own. Java serialisation is one of the worst for comparibility but annoyingly the default. And one of the worst perfomance wise. This is why its so good to provide this customisation, as users anyhow many time do their own, be it json, avro, thrift of the object. Just clunky currently. Look at the success here of Kakfa with this flexibilty. Thus why ability to set a custom serialiser at factory level would be so useful. Sent from my Samsung Galaxy smartphone.
