Re: SAX: New Idea for Entity Resolution
David Megginson wrote: > * Both Byte and Character streams > > Pro: - keeps everyone happy > > Con: - requires more interfaces > - requires another method in the Parser interface > - requires a new SAX class encapsulating a ByteStream and its > recommended encoding (or perhaps the ByteStream interface > will have a getEncoding() method) > - will greatly complicate the EntityResolver mechanism (the > application will need to be able to return a byte stream _or_ > a character stream -- how could I handle this?) You could just have a class that encapsulates a structure with three members: - a CharacterStream - a ByteStream - a String At least one of the CharacterStream and ByteStream must be non-null. If the ByteStream is non-null the String can specify the encoding. James xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format