Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Summary:</strong></p> <ul> <li>WCF for server side</li> <li>Any database and client framework r good to go</li> <li>Client works with local database and there is background process to synchronize new data and get edit permissions.</li> <li>Server business logic level controls conflicts and solves them (automatically) or by informing clients.</li> <li>There is quite few situations when it is better to solve conflicts on database level.</li> </ul> <p><strong>Full answer</strong></p> <p>Really dont see any need in any exotic addons.</p> <p>As i see u r building client side application with server side synchronization. WCF ll be very good choice and whatever application framework u ll use is ok, even if it ll be win8 metro application)</p> <p>Of course there ll be 2 databases client side and server side. U can choose any database that suites needs of ur application best. It could be different server and client side databases.</p> <p>Client gets information from server and posts new data(and data change requests) to server using WCF API.</p> <p>I recommend to make user to work directly with local database and use async requests for server synchronization. Then ur application will run more smooth, no annoying lags.</p> <p>So ull have two business logic parts of your application. One to interact with user give and store his data and another to synchronize all data in background.</p> <p>What about conflicts in data? I think that the best way to solve such conflicts is too solve them in business logic level of ur server. There is quite few situations when it is better to solve conflicts on database level.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload