Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > .NET Web Services
| Search | Today's Posts | Mark Forums Read
.NET Web Services Discussions about .NET XML Web Service technologies including ASMX files, WSDL and SOAP.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Web Services section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old March 2nd, 2005, 11:30 AM
Authorized User
 
Join Date: Mar 2004
Location: , , United Kingdom.
Posts: 25
Thanks: 0
Thanked 0 Times in 0 Posts
Default Web Services Versioning

Hi All,

Does anyone have an views on web service versioning? I am trying to decide upon a web service versioning strategy and at the moment have come up with there is basically no such thing as versioning a web service and to make the service backward compatible you basically have to generate a new web service and point your new clients to that one and keep supporting the existing one untill you move all those clients over.

Any ideas??

Rob

  #2 (permalink)  
Old March 2nd, 2005, 11:37 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

That's it from the way I see it. In order to keep your web service backward compatible you just have to make sure that you don't break the interfaces to it (i.e. don't change the web method signatures).

It almost sounds like you are also talking about moving a web service to a different location (different address). Is this correct? In that case then backward compatibility means keeping the old address available as you said.

-Peter
  #3 (permalink)  
Old March 2nd, 2005, 12:08 PM
Authorized User
 
Join Date: Mar 2004
Location: , , United Kingdom.
Posts: 25
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Peter,

Well what i have found is there are two types of changes that can occour, minor and major. Minor changes allow you to carry on and not break the client, so updates to namespace etc are not really required as the client should still work, you could infact for instance if you have a new method you want to add, specify that in a different namespace, but i wont go into that. The major updates however will almost certain to break the client, and this is when a new end point for new clients would be introduced. From what i have read this is probably all that can be done. Not sure if anyone agrees or not, would be good to have some feedback.

Rob



Similar Threads
Thread Thread Starter Forum Replies Last Post
Assembly Versioning balesh.mind ASP.NET 2.0 Professional 5 October 9th, 2007 10:59 AM
Automatic Versioning in AssemblyInfo piyushnu Assembly Language 1 April 16th, 2006 02:36 PM
web services yanis97 J2EE 0 April 12th, 2006 08:38 AM
Web services hrudanand Apache Tomcat 0 March 27th, 2006 02:08 PM
Web Services Error (Ch18) - No Web Disc. Info. ElPato BOOK: Beginning ASP.NET 1.0 2 April 13th, 2005 03:27 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.