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

ISSUE-65 (EXI compatibility): Allow EXI as characterization for XML in the JMS body ? [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 09 Nov 2010 22:43:01 +0000
To: public-soap-jms@w3.org
Message-Id: <E1PFwu5-0006s2-Q5@barney.w3.org>

ISSUE-65 (EXI compatibility): Allow EXI as characterization for XML in the JMS body ? [SOAP-JMS Binding specification]

http://www.w3.org/2002/ws/soapjms/tracker/issues/65

Raised by: Eric Johnson
On product: SOAP-JMS Binding specification

>From email:

http://lists.w3.org/Archives/Public/public-soap-jms/2010Nov/0004.html

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 22:43:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:25 GMT