[mythtv-users] Mooting architecture for a DataDirect replacement

[Jay R. Ashworth]

On Fri, Jun 22, 2007 at 10:13:27AM -0400, Dan Ritter wrote:
> On Fri, Jun 22, 2007 at 09:37:33AM -0400, Jay R. Ashworth wrote:
> > Sure.  I was, originally, actually planning on just having one
> > newsfroup, and taking the efficiency hit of having machines have to
> > grab all the new headers to see what to get -- because I was planning
> > on having Supernews and the like carry it.
> 
> There's probably a decent argument for having a small hierarchy.

If we can get entire-hierarchy carriage, sure.  I'm not intimately
involved with 'backbone' thinking these days.

> Dividing by time zones or geography seems like a good first
> stab:
> 
> alt.updates.mythtv.na.eastern
> alt.updates.mythtv.na.central
> alt.updates.mythtv.na.mountain
> alt.updates.mythtv.na.pacific
> alt.updates.mythtv.na.hawaii
> alt.updates.mythtv.na.alaska
> alt.updates.mythtv.na.satellite
> 	
> Why different for Hawaii and Alaska? Because I don't think
> their non-satellite television has a whole lot of overlap --
> though I may be wrong.

As it happens, those are time-zone names.

But someone else suggested giving each program source it's own
newgroup, which, while it expands the field, makes the parsing easier.
It's an architectural decision, depending on facts not yet in evidence.

> And why the .na. in the middle? Because the overlap in
> programming between Washington DC and La Paz is probably
> small. And satellites visible across the US, northern Mexico and
> southern Canada are probably not visible from Rio de Janeiro.

Indeed.

Did you make up "alt.updates"?  Cause that's nice.

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