Jason Tackaberry wrote: > I've committed my kaa.epg2 work under WIP/epg2. The API is probably a > bit too tailored to my setup (or North American setup), so it'll likely > need some tuning, but that's not a big deal.
I will try. > * Split into client/server (GuideClient/GuideServer) and uses > kaa.base.ipc for communication. What about supporting reading in a thread of the same app? > * Use libxml2 for xml parsing. Updating from a 17MB xmltv file takes > 95 seconds instead of 74 minutes. Seriously. Because something is missing. You just add a program to the db. But you need to check if it is already in it. Or if something changed (e.g. shows moved around). So the code of _add_program_to_db needs to query the db first. > * Implement zap2it datadirect backend. North America users no longer need > xmltv. Please check permissions of that. I don't care if xmltv violates copyright somehow, but I don't copyright violations in kaa. > * The API is a bit different. It avoids __getitem__ which is a clever > interface but perhaps a bit too clever. :) > * Updating from backend is asynchronous. Downloading / parsing is done > in a thread, and the database is updated in steps within the main loop. Why do you call parse_channel and parse_programme in the main loop? > * GuideClient can used in the same process as GuideServer and will avoid > the unneeded IPC calls. So I can use this to read the db from within freevo. Great. And is the db itself (sqlite) a thread? It could block. > Some examples: [...] If I have the time, I will test it later today. Dischi -- WARNING: I cannot be held responsible for the above, as apparently my cats have learned how to type.
pgpHtxx5GI4BK.pgp
Description: PGP signature
