RE: Converting &, >, <, ", and other odd-ball characte

That is what I did, and it works. I guess when a site is done properly, it
will handle "less" traffic than if the fields were not escaped? All that
String processing must eat up time..I mean, if you have 1000 people all hit
the same page at the same 1 second period of time, that is x number of
fields x 1000 requests all being processed through this one method call. I
made it a static final method to speed things up a bit, but I wish there was
a way to tell the XML parser "if you see & replace it with &, if you
see...". I take it there is no way at the top of an XML page to tell the XML
parser to convert these characters?

Thanks again.


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Michael Kay
> Sent: Thursday, February 15, 2001 4:57 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Converting &, >, <, ", and other odd-ball
> characters...
>
>
> > 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
>


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