Home/ Questions/Q 76257
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T20:38:42+00:00

I have 50+ kiosk style computers that I want to be able to get

  • 0

I have 50+ kiosk style computers that I want to be able to get a status update, from a single computer, on demand as opposed to an interval. These computers are on a LAN in respect to the computer requesting the status.

I researched WCF however it looks like I’ll need IIS installed and I would rather not install IIS on 50+ Windows XP boxes — so I think that eliminates using a webservice unless it’s possible to have a WinForm host a webservice?

I also researched using System.Net.Sockets and even got a barely functional prototype going however I feel I’m not skilled enough to make it a solid and reliable system. Given this path, I would need to learn more about socket programming and threading.

These boxes are running .NET 3.5 SP1, so I have complete flexibility in the .NET version however I’d like to stick to C#.

What is the best way to implement this? Should I just bite the bullet and learn Sockets more or does .NET have a better way of handling this?

edit: I was going to go with a two way communication until I realized that all I needed was a one way communication.

edit 2: I was avoiding the traditional server/client and going with an inverse because I wanted to avoid consuming too much bandwidth and wasn’t sure what kind of overhead I was talking about. I was also hoping to have more control of the individual kiosks. After looking at it, I think I can still have that with WCF and connect by IP (which I wasn’t aware I could connect by IP, I was thinking I would have to add 50 webservices or something).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Unless you have plans to scale this to several thousand clients I don’t think WCF performance will even be a fringe issue. You can easily host WCF services from windows services or Winforms applications, and you’ll find getting something working with WCF will be fairly simple once you get the key concepts.

    I’ve deployed something similar with around 100-150 clients with great success.

    There’s plenty of resources out on the web to get you started – here’s one to get you going:

    http://msdn.microsoft.com/en-us/library/aa480190.aspx

    • 0