[mythtv-users] Mooting architecture for a DataDirect replacement

[Jay R. Ashworth]

On Thu, Jun 21, 2007 at 11:23:42AM -0500, jedi at mishnet.org wrote:
> > On Wed, Jun 20, 2007 at 03:42:47PM -0700, Yeechang Lee wrote:
> >> Jay R. Ashworth <jra at baylink.com> says:
> >> > One of the *most* important characteristics of AIRING data for the
> >> > PVR market is that you want to [continue to] propagate changes to
> >> > the audience just as *late* as you possibly can -- 5 minutes before
> >> > airtime is not unreasonable, nor impossible, if you pick the right
> >> > transmission architecture.
> >>
> >> I inserted a key omitted phrase in the above because, of course,
> >> lineup changes ought to be propagated ASAP *and on an ongoing basis*.
> 
> Changes can be presented by themselves and picked up by any interested
> parties. It could just be a "differential" from the last full dump of
> the schedule data.
> 
> Take the master copy plus the latest changes.

Well, the *real* question is "how far back/forwards" do you need to
go... but remember how Usenet servers *work*.  You can pull, from the
server, as much cached older sked data as you need, in posting order,
and process it.  The subject lines can be machineable, so you can
figure out which data you don't already have, too.

That way there *isn't* really a "full dump" or a "master" copy.  All
there is is "new items"... which could expire 12 hours after their
airdate, as well.

Leveraging RFC1036 and NNTP to move blocks of airing data seems to have
quite a number of advantages, operationally.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274