Differences between revisions 5 and 6
Revision 5 as of 2005-07-28 16:31:01
Size: 2054
Comment:
Revision 6 as of 2009-09-20 22:48:12
Size: 2054
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Binary Serializations of the XML infoset

Axis2 is built on top of a XML info-set representation called OM and is independent of the angle bracket representation of the XML info-set. It is possible to have the Axis2 to work on the one of the other representation XML infoset. Among them the binary serialization is very important as it can yield high performance.

Axis2 reads the information via the XMLReader in the Stax interface and write the information via the XMLWriter interface. So the task of implementing the binary serialization support to Axis2 can be achieved by implementing an XMLReader and XMLWriter that reads and write to Binary representation of XML.

Among the Binary representations that are important to us may be

http://www.w3.org/2003/08/binary-interchange-workshop/Report.html#papers

Another reason this could be very important:

My belief is that binary XML infoset only shows its real benefit with a typed pull parser. The reason: suppose you have a binary encoding of an integer, and then you use a string-based parser, you will end up decoding the binary into an int, converting to a string for the parser API and then back to an int in the deserialisation code.

I (DennisSosnoski) would personally disagree with the above assessment. A typed pull parser would definitely be nice, but even without this you can get substantial size and performance gains from a binary format. See my articles on devWorks at http://www-128.ibm.com/developerworks/xml/library/x-trans1.html and http://www-128.ibm.com/developerworks/xml/library/x-trans2/index.html for examples.

FrontPage/Axis2/Tasks/BinarySerialization (last edited 2009-09-20 22:48:12 by localhost)