It is very good to hear you are planning to improve the entire teletext module!
Quote:
Originally Posted by misterd  The TVServer uses a cache for all pages including all subpages. The main problem of the slow startup is that the TVServer only starts to cache the pages, when you start the teletext module. If you have started it and don't change the channel the TVServer still grabs all pages. If you change to a new channel then you have to start the teletext module before the caching process starts again.
I don't know why the server doesn't start this caching process when you start watching a channel. Since this must be done somewhere in the TVServer, I can't promise anything. |
It would naturally be very good to have the teletext caching start directly (soon) after a channel change. I don't know the CPU requirements and the potential impact of having the chaching start during the channel change but just after playback has started a chaching should be able to run with minimal impact on system performance.
Why is the chache built as a memory bound parameter? Ie why not store the cache in the database? From my experience a teletext page doesn't change that often, and if you zap between two channels you don't need to rebuild the entire chache. Storing the teletext chache in a database would cost some harddisk but all things considered not that much and there would be a fraction higher latancy to retrieve the pages.
Anyhow just something I have been thinking about.
Quote:
Originally Posted by misterd This is why I'm want to change from the keycodes to the internal ACTIONS. They can be better used by remotes etc. |
Oh, I see, excellent!