> My questions now are 1) Right now I'm using DOM to encode my XML;
> is SAX faster?
Often times yes, and SAX consumes less memory.
> 2) Are there any CF configuration parameters I can change
> to improve performance?
I would look at the query->xml part. How are you doing that?
> 3) I'm converting my DOM object to a string so
> the results can be consumed by any client; is this the way to ensure
> platform neutrality or is there a better way to do this?
String is good, however, why make a DOM at all?
> 4) Are there any
> other issues I'm overlooking?
You'll probably get a good speed increase by not building a DOM then
making a string - you might thing about just making a valid xml string.
Also I've written a java query->xml cfx tag, and have been told by a
couple people it greatly increases the query->xml part of what you are
doing. You might think about doing a java or c++ implementation for that
part if it turns out that is the problem.
Good luck,
--
Rob <[EMAIL PROTECTED]>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
