"J. Cairn" <jc****@clearhelp.comwrote in message
news:11*********************@f16g2000cwb.googlegro ups.com...
I am developing an ASP page for clients. I will host the page on my
server, but it must appear on the clients' websites. That means that
the user should not be redirected to my site, but instead should remain
on the client's site. Or at least appear that they are remaining on the
client's site.
One thing that would be acceptable is to host the page on the client's
site, but have it hit my site to get the data. I have looked into
XMLHTTP and also just having the ASP page hit a remote SQL Server
instead of a local one, but haven't made any decisions yet.
Any input is appreciated.
You won't want to be running remote SQL Server calls from their site to
yours. It means openning dangerous ports on the firewall.
Using XMLHTTP (or more specifically ServerXMLHTTP) is the appropriate tool
for the job.
You are creating a Web Service for your clients site to consume.
Think in terms of XML messages passing between your client site and your
server site.
The ASP page on the client site creates an XML DOM containing query
parameters and/or input data. Posts the DOM to your server via
ServerXMLHTTP. You server receives the post extracts the parameters/data.
It the performs approriate database activity and generates an XML DOM from
the results. It sends the DOM back to the client. The client uses the
responseXML property of the ServerXMLHTTP object to retrieve the response
DOM and uses it in building the HTML response to the client.