Client - Server Architecture
I'm designing a system that requires some sort of Client - Server architecture. The synareo is this;
Each client is connected to at least one tape drive. The clients read data off the tape drives, process it and log the data on a centralised database. There can be potentially 100s of clients. I'm expecting the clients to be local to the server, i.e. on the same LAN.
Once the clients are installed on the machines they will need to be registered with a server. This server will be accessed via a web page and have total control over all the clients. The server needs to keep tabs on the various states of all the clients as well as the ability to coordinate them, start them up an shut them down etc.
I will be developing this in C#.Net and am looking into usung WCF or Web sevices. This differs from most of the examples I'm able to find in that all the work and processing is done at the client side and the server is used mearly as a means to control the clients rather than process and data.
Any pointers as to how I might start to tackle this would be great!