Does anyone have suggestions on refactoring web services interfaces? I am interested in best practices for not only versioning interfaces, but for gracefully deprecating methods as well.
For example, SOAP does not permit overloaded methods; each message name must be unique. If I want to create an overload for a method Foo() such as Foo(string), I would need to alter the message name of the latter. Also, if I want to indicate to my service's consumer that Foo() is deprecated in favor of Foo(string), I am not certain as to the best approach.
Thoughts, gang?
- Mark