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.