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 Regards, JB BUGEAUDReceived on Tuesday, 9 November 2010 10:53:39 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:25 GMT