I’m building a touch screen kiosk application in .NET (C#, WPF). the app itself is pretty trivial, it just collects user information.
But here’s where i am getting out of my comfort zone. The kiosk will be set up at remote locations, so with what I know of web development (that’s what pays my bills) I can’t find the kiosk but if I have a central location (web server) it can find me. When the event the kiosk is used for ends, I need it to upload a list of the users to a central repository. I am guesssing ftp over ssl might work, or since I have control of the app possibly a VPN client on the host machines to tunnel through to the central server, maybe using file sharing. These are just guesses, I am used to the opposite model (request from a central server). Any advice to point me in the right direction would be greatly appreciated. I need to implement this in code with limited user interaction. And I have no idea what the architecture of the networks the kiosk can be set up on will be like.
Thanks in advance,
Frank
I would agree with Allon on using WCF. I’ve worked previously on a similar kiosk system using silverlight and a WCF service. We used HTTPS throughout and added unique values to the kiosk’s user agent string to identify which kiosk the request came from for logging purposes.