2006-02-23, 07:49 PM
A thought on a possible changes to the enhanced web interface.
When I use the web interface I get "stuttering" of the active Live TV display and audio. This occurs with a database size as small as 10MB and becomes more pronounced as the DB size grow. Thus I attribute it to the time the web interface takes to search the database for display data.
Every time the user goes back to functions like TV Guide, Manage Recording, etc, the display is recreated resulting in more load on the host and the database. How about simply "show/hide" the existing display once it's created rather than keep recreating it? For example selecting "Episode Search" would simply "hide" the active guide window. Reselecting TV Guide would "unhide" the guide window. Certainly in the case of the TV Guide things aren't going to have changed every time the display is used. If the user thinks there has been a change they can always refresh the display. I've used this technique on a number of web interface displays to save regenerating the display each time the user switches context; in my case not so much to save database load but to save the time to retransmit lengthy relatively static displays.
When I use the web interface I get "stuttering" of the active Live TV display and audio. This occurs with a database size as small as 10MB and becomes more pronounced as the DB size grow. Thus I attribute it to the time the web interface takes to search the database for display data.
Every time the user goes back to functions like TV Guide, Manage Recording, etc, the display is recreated resulting in more load on the host and the database. How about simply "show/hide" the existing display once it's created rather than keep recreating it? For example selecting "Episode Search" would simply "hide" the active guide window. Reselecting TV Guide would "unhide" the guide window. Certainly in the case of the TV Guide things aren't going to have changed every time the display is used. If the user thinks there has been a change they can always refresh the display. I've used this technique on a number of web interface displays to save regenerating the display each time the user switches context; in my case not so much to save database load but to save the time to retransmit lengthy relatively static displays.
ASUS A7V880, Athlon XP 3000+, 1024MB, 250GB (Prog/DB), 40GB (Buffer/Temp), 670GB SATA (Video Library), PVR150MCE Video (2), NEC DVD+/- RW, Liteon DVD, nVidia FX5600 AGP, Onboard AC 97 Audio, Hauppauge Remote, Girder, USBUIRT,802.11G WLAN, nVidia Platinum Decoders