• From: "Bill la Forge" <b.laforge@j...>
• To: <xml-dev@i...>
• Date: Mon, 17 Jan 2000 18:21:07 -0500

> > I'd go further; based on having written a parser, it seems to
> > > me that the only sane tactic is for the parser to use
> > > java.intern(), but only once for each unique name, with some
> > > sort of internal char[] or equivalent table.  If this is
> > > true, it's an even stronger argument for just saying "element > types and
> > attribute names coming out of the parser are intern
> > > ()ed, period".

I suspect the java intern doesn't use weak references. And if
it doesn't, this is a great way to kill server-side XML processing!

Bill


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.

• Follow-Ups:
  • Re: String interning /servers
    • From: james anderson <james.anderson@m...>
  • Re: String interning (WAS: SAX2/Java: Towards a final form)
    • From: Tyler Baker <tyler@i...>

• References:
  • RE: String interning (WAS: SAX2/Java: Towards a final form)
    • From: Miles Sabin <msabin@c...>
  • Re: String interning (WAS: SAX2/Java: Towards a final form)
    • From: Tyler Baker <tyler@i...>

• Prev by Date: Re: String interning (WAS: SAX2/Java: Towards a final form)
• Next by Date: Re: Simple XML conformance
• Previous by thread: Re: String interning (WAS: SAX2/Java: Towards a final form)
• Next by thread: Re: String interning (WAS: SAX2/Java: Towards a final form)
• Index(es):
  • Date
  • Thread