构建 .NET kiosk 应用程序
我正在 .NET(C#、WPF)中构建触摸屏信息亭应用程序。该应用程序本身非常简单,它只是收集用户信息。
但这就是我走出舒适区的地方。该信息亭将设置在远程位置,因此根据我对网络开发的了解(这就是我的账单),我找不到该信息亭,但如果我有一个中心位置(网络服务器),它可以找到我。当使用信息亭的活动结束时,我需要它将用户列表上传到中央存储库。我猜测 ftp over ssl 可能会起作用,或者因为我可以控制该应用程序,可能是主机上的 VPN 客户端,可以通过隧道连接到中央服务器,可能使用文件共享。这些只是猜测,我习惯了相反的模型(来自中央服务器的请求)。任何为我指明正确方向的建议将不胜感激。我需要通过有限的用户交互在代码中实现这一点。我不知道可以设置信息亭的网络架构是什么样的。
提前致谢, 坦率
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
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我同意 Allon 使用 WCF 的观点。我之前曾使用 silverlight 和 WCF 服务开发过类似的信息亭系统。我们自始至终都使用 HTTPS,并向信息亭的用户代理字符串添加唯一值,以识别请求来自哪个信息亭,以用于记录目的。
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.
Kiosk 软件可以很好地映射到 HTTP 请求-响应性质。您的整体架构可以由 2 个主要功能组成:
您可以在 WPF 中编写 UI 并使用 .NET HTTP 客户端执行 HTTP 请求。请参阅
System.Net
程序集中的类WebClient
引用。Kiosk software can be mapped to HTTP request-response nature very well. Your overall architecture can be comprised of 2 major functions:
You can write UI in WPF and use .NET HTTP client to perform HTTP requests. See class
WebClient
reference inSystem.Net
assembly.