W3C home > Mailing lists > Public > public-soap-jms@w3.org > November 2010

Allow EXI as characterization for XML in the JMS body ?

From: Jean-Baptiste Bugeaud <bugeaud@gmail.com>
Date: Mon, 8 Nov 2010 19:40:58 +0100
Message-ID: <AANLkTimCxXSJQZmkMJ45z-6_NLNw_qzbFzFz3GLDgwqL@mail.gmail.com>
To: public-soap-jms@w3.org
Dear SOAP-JMS Editors,

Could it be possible to allow EXI characterisation (see
http://www.w3.org/TR/exi/) in the message body 2.4 as well ?

Using EXI makes sense in a JMS context for any mission critical system
where latency has to be kept at a the minimum.

EXI would also help a lot :
 - keeping XML processing CPU overhead low (message inspection for
active routing for instance)
 - handling & streaming of huge attachement (base64bin saved as octet
binary set for instance)
 - etc

Received on Tuesday, 9 November 2010 10:53:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:22 UTC