[mythtv-users] Mooting architecture for a DataDirect replacement

[ICMan]

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?

This can act as a frontend to almost any type of data store, you just
need the hooks into each type of store.

ICMan

On Mon, 2007-25-06 at 01:54 +0000, bha at att.net wrote:

> Apologies if it's been mentioned before, but has anyone considered jxta (p2p) for the transport mechanism? (http://www.jxta.org/). There are implementations for java, c, c++, even c#.
> 
> Dan
> 
> 
> 
> From: Rod Smith <mythtv at rodsbooks.com>
> Subject: Re: [mythtv-users] Mooting architecture for a DataDirect
> 	replacement
> 
> On Sunday 24 June 2007 02:45, Peter Schachte wrote:
> ...
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070626/3d27dc8d/attachment.htm