Afternoon,
I have a ObjectDataSources tied to a xyz.service at design time by adding webRef.
At runtime is it possible to change the URL of xyz.service.
I have SAME service running on multiple servers, and transactions are site specific so based on transaction type I have to switch the URL of the WebRef added at the desgin time or initially added on web.config.
Any other alternate or help would be appreciated.
Regards,
ZEB
qzeb:
Afternoon,
I have a ObjectDataSources tied to a xyz.service at design time by adding webRef.
At runtime is it possible to change the URL of xyz.service.
I have SAME service running on multiple servers, and transactions are site specific so based on transaction type I have to switch the URL of the WebRef added at the desgin time or initially added on web.config.
Any other alternate or help would be appreciated.
Regards,
ZEB
qzeb --
Here is an alternate design that might solve your design problem.
For such a design, one could probably use just one web service as a TrafficRouter. All web service consumers call the same service, the TrafficRouter, passing in a parameter that is TransactionType. Have the TrafficRouter run the switching logic and route to the correct URL (or ClassLibrary code) based on the given TransactionType. One could manage the set of URLs in the TrafficRouter's web.config file, (provided the list of URLs is not too long) or one could keep the URLs in a database and have the TrafficRouter lookup the correct URL based on the given TransactionType key. And so on.
This pattern has the added advantage of minimizing surface area exposure, which is a generally desirable design goal. All one has to do is expose one web service, the TrafficRouter. The others services can live securely behind a firewall on the friendly site of the physical architechture.
HTH.
Thank you.
-- Mark Kamoski
Thanks for quick response; I had thought about it; but its kind of late & worth to Explore around.
Regards,
ZEB
0 comments:
Post a Comment