this is called interactive digital signage. there are many companies out there. Cisco and Scala are the obvious large players, but quite expensive. if you want to develop a solution, i'd recommend looking at flash with a very critical eye. Air and FlashPlayer have significant memory handling issues when running running 24/7 which is not their intended context and CPU requirement when running fullscreen . (i have hundreds of stbs deployed to customer locations and flash is 90% of my problems).
as a quick look, i'd recommend a combinaison of the following technologies:
server:
apache for content,
samba of nfs for videos (streaming is over-rated when you work on a lan )
client:
mplayer (vdpau (hardware accel) is very usefull for playing hd content on cheap hardware)
and mplayer can be embedded and used as a mozilla plugin on linux.
nvidia video cards (vdpau)
xulrunner
if flash is a must for user-interface animation and accessible to interface artists, use it within xulrunner and make sure you close-and-open the process when possible (killing xulrunner is a easy way to go around the memory issues)
Slashdot Mirror
this is called interactive digital signage. there are many companies out there. Cisco and Scala are the obvious large players, but quite expensive. if you want to develop a solution, i'd recommend looking at flash with a very critical eye. Air and FlashPlayer have significant memory handling issues when running running 24/7 which is not their intended context and CPU requirement when running fullscreen . (i have hundreds of stbs deployed to customer locations and flash is 90% of my problems). as a quick look, i'd recommend a combinaison of the following technologies: server: apache for content, samba of nfs for videos (streaming is over-rated when you work on a lan ) client: mplayer (vdpau (hardware accel) is very usefull for playing hd content on cheap hardware) and mplayer can be embedded and used as a mozilla plugin on linux. nvidia video cards (vdpau) xulrunner if flash is a must for user-interface animation and accessible to interface artists, use it within xulrunner and make sure you close-and-open the process when possible (killing xulrunner is a easy way to go around the memory issues)