[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: String interning
David Brownell writes: > If the concern is only memory efficiency, then I tend to agree > that there may well be more important things to worry about. > But maybe not; so the filter can benefit from knowing if the > data it gets is already interned. That's just the question. I think it's too much hassle for people to have to do boolean namesAreInterned = xmlReader.getFeature("http://xml.org/sax/features/interned-names"); and then if (name == "foo" || (!namesAreInterned || name.equals("foo"))) { do something } every time they want to compare names, and I very much doubt that people will be happy with private final static String FOO = mySAXInternTable.intern("foo"); and then if (name == FOO) { do something } One of the basic design goals of SAX 1.0 was to keep the interface simple, under the assumption that many (most?) of the users will not be XML or Java gurus, or even well-experienced programmers in general. Keeping this goal in mind, then, there are only two reasonable choices: 1. Declare that SAX2 names must always be interned as with java.lang.String.intern. 2. Declare that SAX2 names need not be interned as with java.lang.String.intern. Them's the choices. All the best, David -- David Megginson david@m... http://www.megginson.com/ 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/ or CD-ROM/ISBN 981-02-3594-1 Please note: New list subscriptions now closed in preparation for transfer to OASIS.
|
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
|