[mythtv-users] Mooting architecture for a DataDirect replacement

Peter Bowyer peter at bowyer.org
Tue Jun 26 12:56:28 UTC 2007


On 26/06/07, ICMan <icman at eol.ca> wrote:
>
> The solution with the best model is DNS.  I am not suggesting we use DNS
> servers and add an extra set of record types (though that has some merit),
> but using the DNS model (and maybe a tight server as the base of the code,
> like tinyDNS or somesuch) allows a distributed heirarchy of servers, a
> common transport format,  JIT information updates (depending on the timeouts
> on your local server), the ability for redundant data storage - for huge
> numbers of transactions consisting of relatively small amounts of data (most
> hits will be differential data), DNS rules the Internet.  Literally.  With
> the properties of such a mechanism, why is it not being seriously considered
> on this list?

Because it was designed for lightweight, moderately static data. As
soon as you start loading DNS up with big records and the UDP queries
have to become TCP queries, the advantages of the mechanism fall away.

Just because DNS is good at caching sub-128-byte name resolution
queries, doesn't make it the right thing to use to move (relatively)
heavy listings data around.

Nail and hammer syndrome in evidence here.

Peter

-- 
Peter Bowyer
Email: peter at bowyer.org


More information about the mythtv-users mailing list