getdata.xml vs getdata.asp

As I've started to use XML more extensively for data transfer to web
pages, I have started to use the XMLHttpRequest object to get data
from the server. Since I want the data to be returned as XML, I have
been playing around with http: requests to SQL Server. I have also
created ASP pages that return XML after using SQL Server to collect
data.
As far as I know, these two methods are approximately equivalent. ASP
clearly has some important advantages over SQL Http requests,
maintaining session information immediately comes to mind, but does
the convenience of ASP come at a high enough cost that I should
consider using SQL Http requests?
I should clarify the question: I'm your typical geek who loves to
learn and use new technology: I'm inclined to use SQL Http requests
simply because they are new and different and I like how they can help
delegate different logical tasks in my project. Am I wasting my
client's money and my own time looking to SQL Http requests for
performance improvements?
TIA for any light you can shed on this...
Chuck Jungmann
"Chuck Jungmann" <NOchuckSPAM@.cpjj.net> wrote in message
news:frepj0ddqr0m68kt7rak5og95lv4dfg3j6@.4ax.com...
[snip]
> Am I wasting my
> client's money and my own time looking to SQL Http requests for
> performance improvements?
As with all technology, most things are a compromise. SQLXML is no
exception. I would suggest looking at the pros and cons and then choosing
the method that best suits your needs.
SQLXML vs. ASP pros:
1) Less layers (possible speed increase)
2) Not scripted (possible speed increase)
3) SQL and XML knowledge only
SQLXML vs. ASP cons:
1) Less flexible.
2) Possibly more vunerable to attacks (less testing and real-world use than
ASP)
3) Upgrade path somewhat unclear at the moment (although it looks like 2005
will provide a good upgrade path to SQLXML HTTP).
I would also suggest doing some performance tests and reliability tests to
see how your two methods measure up. I don't think your testing is a waste
of time.
Bryant