Hi,
Last year I developed a “Device Manager” application that managed the
configuration of devices mounted in a 19” equipment rack. This application
is a standalone Windows Forms app written in C# that uses Binary
Serialization for persistence and an Observer/MVC design for the User
Interface. In other words, on startup the entire Object Model of entity
objects is created from the binary file (like an in-memory OO database) then
the UI/View subscribes to this model so that any changes are displayed. This
application works great. However, now I need to enhance this design to
support about 5 clients. The clients will still be Windows Forms apps and on
the same LAN. This is an obvious candidate for .Net Remoting. However, now
that WCF has been released it’s probably the better choice? I want the
clients to behave just like the standalone UI did (i.e. Observer/MVC). What
is the best way to go about distributing these entity objects to all of the
clients and synchronizing among them? The entity objects will need to be
Singleton objects on the server. Would WCF callbacks be appropriate here?
Would manual locking of server objects via client be appropriate? Any
thoughts/comments will be greatly appreciated.

Thanks, Jeff

=?Utf-8?B?Qm9nZXlHb2xm?= <BogeyGolf@discussions.microsoft.com> wrote in
news:EA904483-3F80-4317-8C94-AC609E372348@microsoft.com:

[quoted text, click to view]

I would use WCF ... it provides all the functionality remoting did and then

Thanks for the feedback.
Please note, I moved this post to dotnet.distributed_apps.


[quoted text, click to view]