> So the solution our team has come up with is on every field
> of every page
> that can possibly have any of these non-html friendly
> characters, to call a
> method and replace them. Problem is, String comparing/replacing is
> intensive, and often creates unnecessary objects that use up
> more memory.

That's what you need to do though!

But you can reduce the cost dramatically if you avoid creating a new String
object unless a replacement actually needs to be done.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list