I have computers with 50 kiosk styles that I want to receive in order to receive a status update from one computer on demand, as opposed to an interval. These computers are on the local network in relation to the computer requesting the status.
I researched WCF, but it looks like I will need IIS, and I would prefer not to install IIS on 50+ Windows XP mailboxes, so I think this excludes the use of the web service unless it is possible for the WinForm server to have a web service?
I also studied the use of System.Net.Sockets and even got a barely functional prototype, however I feel that I am not qualified enough to make it a reliable and reliable system. Given this path, I will need to learn more about socket programming and threading.
.NET 3.5 SP1 works in these blocks, so I have full flexibility in the .NET version, but I would like to stick with C #.
What is the best way to implement this? Should I just bite the bullet and find out more sockets or is there a better way for .NET to handle this?
edit: I was about to go with a two-way message until I realized that all I need is one-way communication.
edit 2: I avoided the traditional server / client and switched with inversion because I wanted to avoid consuming too much bandwidth and was not sure what the overhead I was talking about was. I also hoped to get more control over individual kiosks. Looking at it, I think that I can still have this with WCF and connect via IP (I did not know that I could connect via IP, I thought I would have to add 50 web services or something else).
source
share