简体   繁体   中英

Separating a desktop application into a client-server application

I have a multi-tiered desktop application with a well separated modular design. So far it has been working on a single PC, but now the scope was revised to create a distributed system with a server and multiple clients on a local network.

The Client requests historical data as well as real-time data updates by subscribing to various channels.

The Server read the historical data from the database and real-time data from the PLC and sends it to a client. If a client performs any data modifications, the server must notify all the connected clients of any changes.

I have looked into WCF as well as this article: http://www.codeproject.com/KB/IP/TCPServClntCommRMIFrmwrk.aspx

Does anybody have any other recommendations on how to approach this task?

You are describing a typical Client-Server Model with P ublish-Subscribe Paradigm . Look at the articles to get more insight to how similar architectural problems are approached.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM