Supporting Dynamic URLs
One of the ways in which a great deal of sample code falls short of demonstrating how web services are consumed in professional applications is that the samples typically show a hard-coded service URL. Even if the web service being consumed is never scheduled to change its URL, it is possible that domain names could change, the file name of the service could change, and even more likely, the server will change depending on whether you are consuming a test service or a production service. Another possibility is that different vendors provide services that conform to the same contract. Assume, for the sake of example, that three different vendors provide a news publication service. You are building an application that can ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access