SAX: Distributed Implementations

[Eduardo Pelegri-Llopart]

I agree with Dave Brownell about the distribution issues.

The only advantage I see for having a language-neutral SAX is having a
parser, say written in C, called from a client written, say in Java,
all in the same machine (and probably the same process).

There are not that many pairs of interest (to me, I'm a Java
programmer), so I'd *much rather* put the burden on the implementor of
the parser, or of the translation layer, than on the client.

I.e. I'd *much rather* have a SAX/Java that mix best with Java than
a language-neutral SAX.

Of course, it depends on what your goals are.

	- eduardo

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