Design of API
Wondering if anyone has sources that would give me information around how
to iteratively develop my web service without breaking functionality? I
am specificly interested in ideas to solve the problem and industry information
that is available.
e.g. I have a web service that returns result A for United States. Now
I want that service to become global so I want to return result A given
a Locale instead of just returning United States information.
The way that I see it I can create a brand new API (web service) and register
it with the UDDI directory and the client has to be smart enough to go get
the appropriate service.
-- or --
I could add the locale as an optional tag on the request and process appropriately.
If the locale is passed then I return the appropriate information based
on locale or I return United States because that is how my original message
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL