web services - Design pattern for working with different versions of webservices? -


i'm looking design pattern solve architectual issue i'm having.

i use webservices kinda same not exactly. each new version of webservices there might few more methods available, part same.

i want write abstractionlayer works regardless of version of webservices i'm communicating with. if i'm using method exists in newer versions of webservices sort of error, ok. can handle those.

the reason want abstraction layer avoid tight coupling between application , version of webservices communicating with.

what options when comes design patterns abstraction layer? see there 1 pattern called adapter, , 1 called bridge. of in situation? appreciated!

edit - clarity here drawing. enter image description here

sometimes want application talk webservices version 1, , other times want use webservices version 2. depends on using client application.

the client application shouldn't relly know or care version talking to. exception if uses method available in of versions need handle gracefully (tell user have installed old version of webservices).

that factory. use builtin channelfactory or come own. anyway, facttory lets change implementation without changing client's contract.


Comments

Popular posts from this blog

c++ - Function signature as a function template parameter -

algorithm - What are some ways to combine a number of (potentially incompatible) sorted sub-sets of a total set into a (partial) ordering of the total set? -

How to call a javascript function after the page loads with a chrome extension? -