Hi, First, I am not a web service professional.
Second, why should your parameters be expressed in xml? You say for future extension, so your clients do not have to change their api. But this assumption is not valid, IMO. Your clients will still need to program if they want to use your new features. Since I like to program explicit, why not on your webservice api? If you have a newer version, just give that newer version a different url. Clients that only care for version 1 will never be affected. (this is important, since it can become difficult to support more than 1 version from 1 code base...) And clients that want to upgrade to version 2 need to access a different url. How are you all thinking about this? Or I am missing something here? // Ryan ------------------------------------- The information included in this message is personal and/or confidential and intended exclusively for the addressees as stated. This message and/or the accompanying documents may contain confidential information and should be handled accordingly. If you are not the intended reader of this message, we urgently request that you notify Centric immediately and that you delete this e-mail and any copies of it from your system and destroy any printouts immediately. It is forbidden to distribute, reproduce, use or disclose the information in this e-mail to third parties without obtaining prior permission from Centric. We expressly point out that there are risks associated with the use of e-mail. Centric and the companies within the group shall not accept any liability whatsoever for damage resulting from the use of e-mail. Legally binding obligations can only arise for Centric by means of a written instrument, signed by an authorized representative of Centric. ------------------------------------- =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
