[mythtv-users] Mooting architecture for a DataDirect replacement
Dan Ritter
dsr-myth at tao.merseine.nu
Wed Jun 27 14:30:03 UTC 2007
On Wed, Jun 27, 2007 at 04:27:34PM +1000, Peter Schachte wrote:
> Specifically, I don't think replacements want to be like diff entries that say
> "look for something like THIS and replace it with THAT." That's just extra
> overhead, and unnecessary because each program has a date, time, and channel
> that uniquely determines where it belongs. The only tricky problem is handling
> the situation where an update replaces part of the time span of an existing
> program.
Such an update should include every entry on that channel from
the last unaffected program to the first unaffected program.
The two most common situations for this will be:
1. Live sports event runs over time, subsequent programs are
delayed or cut.
2. Presidential address or similar high-news-value event.
The update should look like:
[header, channelid, authentication sig, serial number of this
update, whatever]
[1300-1400, "All Star Spectacular Warmup and Cheerleading"...]
[1400-1935, "All Star Spectacular Event"...]
[1935-2000, "The Simpsons"...]
[2000-2100, "Movie of the Week: The Andromeda Stress"...]
in which the warmup event and the movie are the unaffected
programs, and the entries in between have changed.
Since each record should run about a KB, we don't have an
incredible overhead, and we do get some robustness.
> From the central site, the data could be distributed by NNTP, UUCP, FTP, HTTP,
> P2P, or carrier pigeon.
You'd still want multiple "central sites", but yes.
-dsr-
--
.. .----. -- .-. . .- -.. .. -. --. -.-- --- ..- .-. -- .- .. .-.. .-.-.- .-- .... --- . .-.. ... . .. ... ..--..
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.
More information about the mythtv-users
mailing list