On Mon, 2005-10-17 at 15:41 +0200, Dirk Meyer wrote: > No, we need data from about 6 hours and 10 channels. More doesn't fit > on the screen.
Actually there's a bug with fetching program data between two channels that I have to fix. (It fetches all programs between two database ids, but if the channels aren't listed in order then database ids won't increment the same way channels do.) But in any case, this kind of data isn't much. It can go over IPC easily. > I know, I was saying that it will take some more time. I know the old > parser is bad, but it worked ok for me ... but I only have 10 channels > in it. I have 125 channels and just under 30000 programs representing a week's worth of listings. In reality, I never really cared how long the tv_grab took since it happens when I'm asleep. Only very rarely do I run it manually -- when I do, it's nice that it takes a sane amount of time to complete. > I don't know what source you use. Some xmltv grabber parse a website > and this is not 100% clear if it is a copyright violation or not. I don't see how it's a copyright violation. If the data is published on the web, there is implicit permission to at least copy that data to your computer (which is necessary in order to view it). Processing that data into a database might violate the terms of some license, which could only ever be enforceable if the site requires the user to agree to the license before providing the data. In the case of the zap2it backend, there is no such bypassing of a license agreement. The user must agree to the zap2it terms when he gets an account there. And the terms are pretty reasonable. The backend doesn't circumvent any authentication or other mechanism that might be in place to restrict the data. It's all very above board. > I will play around with it. I found one possible problem: you can only > use sqlite objects (like the cursor) from the same thread it was > created. But I guess I can handle it. I'm only downloading and parsing in a thread. The actual database access happens in the main thread which is where the cursor is obtained. So there shouldn't be any problems there. Cheers, Jason.
signature.asc
Description: This is a digitally signed message part
