[mythtv-users] Mooting architecture for a DataDirect replacement

[Jay R. Ashworth]

On Fri, Jun 22, 2007 at 03:18:16PM -0400, Rod Smith wrote:
> So basically, what MythTV does now with Zap2It is quite similar to what TiVo 
> does, at least for method #3. Method #2 wasn't always used; in TiVo's early 
> days, it was all done via #3. I *PRESUME* that method #2 was implemented as a 
> cost-cutting measure, to reduce load on their server and the bill from the 
> ISP(s) they use to handle user dial-up traffic. Similarly, your method uses 
> NNTP to minimize the costs on the community -- if we wanted to use the same 
> protocols we use now but just set up our own server, we'd need to pay for it 
> in some way. Most of us already pay for NNTP via our ISPs, so it's a logical 
> choice to use to minimize costs.

It is, but that wasn't even my most pressing consideration in picking
it.  I was more interested in the asychronous flooding nature of NNTP
dissemination, which seems perfectly suited for this: you have a
change, you send it, and everyone gets it as soon as possible.

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