I have a web service that is currently being utilized heavily by about 400+ clients. We are thinking of changing our URL to something different but coordinating that change with 400+ people at once isn't going to work since this web service is used 24/7 and requires little down time.
My question is can we put in place domain forwarding to the new URL to redirect those pointing at the old URL until we get everyone updated to the new URL? One possible complication to this is that we are using signed certificates but we are able to handle a change to the certificate within our application. We would also like to avoid creating a dummy web service stub that calls the new URL but if that is the way to go we will pursue that route. We have total control of our hosting, DNS and web servers so any changes required would not be a problem.
Here are some details but I'm not sure they make a difference: .Net 1.1 (but will be at least 2.0 ...
Go to the complete details ...