The format is supposed to be protocol free. Are you really being required to use the CoreMessage between for the conversion of the body?
if you really need it, we could definitely add a protocol on the XML format. We would of course need to implement OpenWireMessage but that's not difficult at all. (It's just that I want to commit what I have now, and then make further implementations). On Thu, Mar 2, 2017 at 6:57 AM, Christopher Shannon <[email protected]> wrote: > Nice work Clebert. I would think the normal use case is that clients are > going to produce/consume in the same protocol so this should be a nice > performance boost. > > This got me thinking...The first version of the KahaDB export tool I am > working on uses the Artemis XML format because it just uses the existing > XmlDataImporter which means we need to convert all messages from OpenWire > to CORE. But with this change we could conceivably add an option to > export the open wire messages in their original format without conversion > in a future update. > > On Wed, Mar 1, 2017 at 3:32 PM, Clebert Suconic <[email protected]> > wrote: > >> If you can actually measure AMQP non persistence before and on my >> branch? :) that would be awesome! >> >> On Wed, Mar 1, 2017 at 1:45 PM, nigro_franz <[email protected]> wrote: >> > +100 an awesome job Clebert!! >> > If you want I will be happy to bench it against the original >> version...But I >> > feel a good vibe here >> > >> > >> > >> > -- >> > View this message in context: http://activemq.2283324.n4. >> nabble.com/DISCUSS-ARTEMIS-1009-Pure-Messaging-Encoding- >> Refactoring-Artemis-2-0-tp4722638p4722667.html >> > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> >> >> -- >> Clebert Suconic >> -- Clebert Suconic
