instance, converts it to an XML string, and sends it off when it receives
a SOAP request. At first it seemed like everything worked fine. I first
created a test CFM page that consumed the service and printed out the XML;
then I created an Excel macro that consumed the service, parsed the XML,
and printed the results out on a worksheet.
Now it seems my web service may not be so scalable. Our DBA recently made
some changes and now the recordset contains at least 10 times more data
(yes the data is valid and I expect the size of the recordset to only
increase). When I try to access the same web service I do not necessarily
get all the XML; the XML string gets cut off at near the very end. This
issue cannot be replicated reliably. (What I do know is that my WS logic
is sound and my query still works.)
So it seems to me the culprit in this matter is the way my service is
coded. My questions now are 1) Right now I'm using DOM to encode my XML;
is SAX faster? 2) Are there any CF configuration parameters I can change
to improve performance? 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? 4) Are there any
other issues I'm overlooking?
Thx for your time...
--
Joe Tseng
Give a man a fish, he owes you one fish.
Teach a man to fish, you give up your monopoly on fisheries.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
