传入请求公共队列的最佳架构？
我们有一个网络应用程序 (ASP)，其中包含工作流程，供管理层将工作分配给个人。问题出现在签出工作之前。在晚上/夜间/清晨，操作人员很少，因此如果其他关键工作是在远离计算机的情况下执行的（从架子上为机械师获取工具），则可能不会密切关注管理工作队列。因此，我们有一个功能要求，即创建一个程序，以便在工作区域的监视器或电视屏幕上不断刷新显示新的未分配工作。
我的问题：部署架构有推荐的最佳实践吗？ Web 与桌面胖客户端应用程序？
Web：
优点 - 保持架构一致
缺点 - 控制盒子可能很困难，我们需要采取额外的步骤来确保盒子不会被劫持到其他站点，控制有限的登录、其他安全和计算机资源
< strong>桌面胖客户端：
缺点 - 现在需要支持 Web 和客户端应用程序。需要将两个实例部署到两个位置
优点 - 安全性和限制盒子的使用很简单。无需应用程序安全登录，因此 PE 等功能可以在需要时恢复应用程序。
We have a web app (ASP) that has workflow in it for management to assign work to individuals. The problem is prior to signing out work. During the evening/night/early morning operations are lightly staffed so the management queue of work may not be watched closely if other critical work is being performed away from the computer (getting tools from shelves for mechanics). So we have a functional requirement to create a program to a continually refreshing display of new unassigned work on a monitor or TV screen in the work area.
My question: Is there any recommended best practices for the deployment architecture? Web vs Desktop Thick Client application?
Web:
Pro - Keeps the architecture consistent
Cons - Control of box may difficult we have take extra steps to ensure the box is not hi-jacked to other sites, controlling limited logins, other security and computer resource
Desktop Thick Client:
Cons - Both Web and Clients apps now need to be supported. Will require two instances deployed to two locations
Pros - Security and limiting use of box are simple. No app security log in required so functions like PE can bring app back up if needed.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我过去创造过类似的东西。我使用了“Jack PC”（http://www.chippc. com/thin-clients/jack-pc/index.asp）并连接了一台大型液晶电视。 Jack PC 配置为使用 RDP 自动连接到服务器，并编写脚本在服务器上启动 Windows 窗体应用程序。 Windows 窗体应用程序基本上是一个带有 WebBrowser 控件的窗体。该应用程序基本上根据预定义的计划调用查询来查找要加载的 URL。还有第二个 Web 应用程序，其中包含具有加载/显示数据逻辑的页面。本质上它可以显示任何 HTML 内容，包括报告。希望这能给你一些想法。
I've created something similar in the past. I used a "Jack PC" (http://www.chippc.com/thin-clients/jack-pc/index.asp) with a large LCD TV connected to it. The Jack PC was configured to automatically connect to server using RDP and scripted to start up a Windows Forms application on the server. The Windows Forms application was basically a form with a WebBrowser control. This application basically called a query according to a pre-defined schedule looking for URL's to load. There was a second Web application that contained pages with the logic to load / display the data. Essentially it could display any HTML content, reports included. Hope this gives you some ideas.
在我看来，这个场景适合观察者模式。这将允许你滚动未来'观察者（移动设备、桌面等），无需重新架构您的核心工作流程应用程序。
Sounds to me like a scenario suited to the Observer Pattern. This will allow you to roll future 'observers' (mobile devices, desktops etc) without the need to re-architect your core workflow application.