SAX: finalising org.sax.xml.Parser
donpark at quake.net
Tue Feb 24 06:09:02 GMT 1998
>I don't think this last one is a good idea. If you want something that
>operates on a stream of characters as opposed to bytes, it should be
> void parse(Reader r, String baseURI)
>Using an array of chars is as bad an idea as it would be to replace the
>InputStream method with a method that operates on an array of bytes.
>I am not convinced this really buys you anything. It's easy enough to
>write an InputStream that takes an array of chars and presents then as a
>sequence of UTF-16 encoded bytes. It also raise some problems since the
>XML spec doesn't define the operation of a processor on an sequence of
>chars. For example, what if anything should the processor do with an
>encoding declaration in this case?
If I remember correctly, what David is trying to do is provide us with means
to parse XML data from a byte stream as well as character stream. Since
Reader will actually hide the byte-based aspect of the data stream, it in
inappropriate for our purpose.
XML character stream is also very useful when XML data is generated and
processed within a framework. In such a system, converting character
streams to byte stream and then converting it back to character stream is
As far as what to do with encoding information when dealing with character
streams, will there be any problem if SAX just ignored it?
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;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev