etienne_marais
Honorary Master
I'm a bit rusty on this, please recommend design pattern.
Application has to operate either by (1)webservice calls [webservice does all the communication with SQL server] (synchronous, asynchronous or both) as well as (2)API calls which speaks directly from the client with the SQL server.
Basically it is two programs in one having the same functionality for the end user. The end user can switch between using webservice calls or API calls at any time (the consideration would be whether http or sql [or bothe] ports are open on the firewall.
Background: A previous silverlight application was developed with only webservice functionality. A current application however was developed with only API (which uses ADO & direct SQL queries). The current application now has to incorporate optional webservice functionality. The original silverlight application has a webservice which defines many datastructures (and methods that use/return them) that are incompatible with the datastructures used in the current API version.
Everything is written in c#, I have decided against interfaces (for now) and am considering virtual classes. But according to which design pattern ?
Application has to operate either by (1)webservice calls [webservice does all the communication with SQL server] (synchronous, asynchronous or both) as well as (2)API calls which speaks directly from the client with the SQL server.
Basically it is two programs in one having the same functionality for the end user. The end user can switch between using webservice calls or API calls at any time (the consideration would be whether http or sql [or bothe] ports are open on the firewall.
Background: A previous silverlight application was developed with only webservice functionality. A current application however was developed with only API (which uses ADO & direct SQL queries). The current application now has to incorporate optional webservice functionality. The original silverlight application has a webservice which defines many datastructures (and methods that use/return them) that are incompatible with the datastructures used in the current API version.
Everything is written in c#, I have decided against interfaces (for now) and am considering virtual classes. But according to which design pattern ?
Last edited:
