There are a lot of places that do this... you can just point to the pages on webserverb probably with an ip address unless you register a domain name to point to it. You could also do a third level domain - and have something like tld.domainname.com.



>hi all,
>i have been asked by a customer to provide a web frontend to a vfp app that they already use. we are going to get an inhouse web server and set up the interface on it but here is the main problem i have. they want to keep their website on webserverA that is currently with their isp but have the sections that link into our application hosted on their own server, webserverB, the reasons that they don't want to host the entire thing themselves are numerous and are not likely to be over come. does anyone know how i can have the website on webserverA, which i have full access to, provide information from webserverB transparently without the user knowing any different? if i have not explained this properly please let me know.
>this is a quick development, tough schedule, so no chance to try the asp.net learning curve.
>Slán
>~M