views:

168

answers:

1

we have a C# wpf based application and want it to be a multi user thingy now. database is ready for it. We have database replication say across 10 sites ...

which is the best architecture for converting this into a multi user application? this is a desktop application.

thank you.

A: 

You have a C# WPF app talking to a database. That's as good an architecture for a multi-user application as you'll need. What you need now is to keep user concurrency in mind when you retrieve/update data. I'd stay away from replication as long as I could.

An aside on your post... do be as specific as you can in your questions. Calling something a "multi user thingy" and over-using terminology such as "something like that" really doesn't help people to understand your problem - just my 2c.

PjL
thnk u for the note .. we hv GUI layer ,data layer and a logic layer that binds these. There are many parts/modules in our product ... to give you an analogy if our product is a about editing tree .. users can be working on trunk, branches, leaves fruits. i need read and write locks based on the working areaAnd this is in multiple geographic locations (example 10 sites). we use DB replication (ms sql server).. but its hard for me to assume that its the same data on all 10 ms sql databases all the time and all the 10 databases have exactly the same data. thank you guys for your help
pskk
Why not put your DB on a central server and expose it through a web service? That way you can manage locking/etc in one place and you don't need to be aware of that on the client? (just a thought).If the comments/answers are helpful, feel free to vote me up :-)
PjL
thanks ... tht would wrk well if we had client server architecture. Since the nodes are distributed, centralized solution, i guess, is not the right choice
pskk