I've got a system i'm designing where we're using 4 specialized PC's we manufacture in house that have 16 serial ports (db-9 RS232) I need to communicate with 64 units near simultaneously (4x16) and manage the communications. Here's the model I came up with and i'm soliciting feedback
Server: Runs on one system and coordinates client applications. Maintains a master state machine and makes sure that the clients are in lock step with that state machine. (For instance, all units do task A, when the last one reports completion, all units do task B).
Communicates via .net remoting? WCF?
Client: Can run on the same system as the server. Manages all the IO. Manages buisness logic for actual task execution (bad idea?) Reports status through Remoting/WCF via notification events (for instance INotifyPropertyChanged).
I've never worked with .net remoting or ANY sort of distributed applications so i'm a total novice at this, but I do learn quickly. Literature and community advice would be much appreciated at this point.