If I have a silverlight application deployed to <http://mydomain.com/MySilverlightApp> I know that I can communicate with a web service using either:

* <http://mydomain.com/Webservices/> or
* <http://mydomain.com/MySilverlightApp/WebServices/>.

If I use <https://mydomain.com/Webservices> I will get a security exception because the site of origin is inconsistent. 

Likewise if I use <http://mydomain2.com/Webservices> I will again get a security exception because of site of origin issues.

I don't have the time to set this up or to test it at the moment but would I get a security exception if I used <http://s1.mydomain.com/Webservices> or <http://s2.mydomain.com/Webservices>?

I'm basically looking for a way to do load balancing but if my app is deployed to one location <http://mydomain.com/MySilverlightApp/> what are the routes to overcome these security exceptions resulting from site of origin differences?