Normal
I'd just like to jump in here to put up my vote for using WCF (or Web Services if Framework 3.0 is not being considered) for client/server communication. If people have been reading the fuzzy recording thread they may have noticed there was a testing problem there because some DLL's on the client weren't updated, when they WERE updated on the server. This gave weird results (obviously).Such a situation would not have occured of the database access was behind a service. Then the client would have automatically picked up the new behaviour of the server.The real challenge would be to get the service API right, simple enough, and as stable as possible. Because if the service contract changes then the client DOES have to be updated.
I'd just like to jump in here to put up my vote for using WCF (or Web Services if Framework 3.0 is not being considered) for client/server communication. If people have been reading the fuzzy recording thread they may have noticed there was a testing problem there because some DLL's on the client weren't updated, when they WERE updated on the server. This gave weird results (obviously).
Such a situation would not have occured of the database access was behind a service. Then the client would have automatically picked up the new behaviour of the server.
The real challenge would be to get the service API right, simple enough, and as stable as possible. Because if the service contract changes then the client DOES have to be updated.
