WCF Versioning Guidelines(wcfpro.wordpress.com)

submitted by arielabarielab(65) 1 year, 4 months ago

Services exist in order to serve external clients. They do so by exposing a wide range of external interfaces which are later used by the clients to interact with the service. After initial deployment, and potentially several times during their lifetime, services may need to be changed for a variety of reasons, such as changing business needs, re-factorization of code, or to address other issues. Each change introduces a new version of the service. Each new service version potentially introduces changes to the external interfaces exposed by the service. Our goal, as developers, is to be able to freely change our service internals (and sometimes, when needed, external interfaces), and on the same time, allow existing and new clients to keep using the service. In order to do so, we need to form a set of versioning guidelines.

1 comment |category: |Views: 328

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by yesthatmcgurkyesthatmcgurk(4063) 1 year, 4 months ago 0

Three people joined just to kick this story. Please, don't be lame.

Reply

information Login or create an account to comment on this story