Rob Shortt wrote: > That's an interesting way of dealing with the EPG. I wonder how much > overhead would be involved. Also I'd suggest not to use XMLTV to > share guide data internally as parsing it takes too much CPU+memory.
Maybe not XMLTV and some other sort of txt format. But I want something not depending on Python (pickle). > I was thinking something a little different for the EPG. I would like > to have a single point on the network for the EPG, as an mbus > app. Using some client protocol that we define, various Freevo > frontends would query the EPG process for guide information. That would be slower than having a host local database. > -Still thinking... /me too Dischi -- It's a little known fact that the Dark Ages were caused by unresolved Y1K issues.
pgpzmKLTLYpM5.pgp
Description: PGP signature
