home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Use WebService between Server and Client
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="dvdfreak" data-source="post: 137295" data-attributes="member: 21313"><p>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).</p><p></p><p>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.</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="dvdfreak, post: 137295, member: 21313"] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Use WebService between Server and Client
Contact us
RSS
Top
Bottom
