SAX: Distributed Implementations

David Megginson ak117 at
Mon Apr 20 20:56:33 BST 1998

David Brownell writes:

 > I'd probably not split a real application in that particular way,
 > though.  The latency penalty for lots of fine grained syntax
 > callbacks hurts, and distributed systems are generally designed to
 > ship bulk data (such as an XML message) and process it locally
 > (such as parse, interpret, respond to some purchase order in XML
 > while updating several databases).  HTTP is only one of the more
 > visible examples of that trend.

This wouldn't be too much of a problem with a remote character or byte
stream, especially since we've removed the single-character and
single-byte read().  AElfred, for example, slurps up 32K at a time
into its read buffer.

By the way, Java is simply the initial implementation for SAX, but it
is not intended to be the only one.  Ideally, I should have used
OMG-IDL from the start, but many more people understand (and can use)
Java, so I started there.  Several people have offered to write
OMG-IDL versions of the interfaces as soon as we're done defining
them.  There is already a Python implementation of an early draft of
the SAX interface, and I might take a stab at the C++ version myself.

All the best,


David Megginson                 ak117 at
Microstar Software Ltd.         dmeggins at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list