ISSUE-65: Allow EXI as characterization for XML in the JMS body ?

EXI compatibility

Allow EXI as characterization for XML in the JMS body ?

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Eric Johnson

Opened on:

2010-11-09

Description:

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

Related Actions Items:

No related actions

Related emails:

1. RE: Agenda for the 2011-01-11 conference call (from Derek.Rokicki@softwareag.com on 2011-01-11)
2. Agenda for the 2011-01-11 conference call (from eric@tibco.com on 2011-01-10)
3. Completion of ACTION-237 (Apply the resolution for ISSUE-65 - EXI) (from M8PHILLI@uk.ibm.com on 2011-01-07)
4. Agenda for 2011-01-04 conference call - Regrets (from peaston@progress.com on 2011-01-04)
5. Agenda for 2011-01-04 conference call (from eric@tibco.com on 2011-01-03)
6. Minutes 2010-12-21 (from M8PHILLI@uk.ibm.com on 2010-12-21)
7. Agenda for 2010-12-21 conference call (from eric@tibco.com on 2010-12-20)
8. Agenda for 2010-12-14 conference call (from eric@tibco.com on 2010-12-20)
9. RE: Agenda for 2010-12-14 conference call (from alewis@tibco.com on 2010-12-13)
10. Agenda for 2010-12-14 conference call (from eric@tibco.com on 2010-12-13)
11. Minutes 2010-12-07 (from M8PHILLI@uk.ibm.com on 2010-12-07)
12. Re: Updated proposal for ISSUE-65, complete ACTION-232 (from ylafon@w3.org on 2010-12-06)
13. Agenda for the 2010-12-07 conference call (from eric@tibco.com on 2010-12-06)
14. Updated proposal for ISSUE-65, complete ACTION-232 (from eric@tibco.com on 2010-12-06)
15. Action-229 complete (from phil_adams@us.ibm.com on 2010-11-30)
16. Proposal to resolve ISSUE-65, complete ACTION-228 (from eric@tibco.com on 2010-11-29)
17. Re: Allow EXI as characterization for XML in the JMS body ? (from eric@tibco.com on 2010-11-29)
18. Agenda for the 2010-11-30 conference call (from eric@tibco.com on 2010-11-29)
19. Minutes 2010-11-16 (from M8PHILLI@uk.ibm.com on 2010-11-16)
20. Agenda for the 2010-11-16 conference call (from eric@tibco.com on 2010-11-15)
21. Re: Allow EXI as characterization for XML in the JMS body ? (from ylafon@w3.org on 2010-11-10)
22. Re: Allow EXI as characterization for XML in the JMS body ? (from eric@tibco.com on 2010-11-09)
23. ISSUE-65 (EXI compatibility): Allow EXI as characterization for XML in the JMS body ? [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-11-09)

Related notes:

Display change log