[mythtv-users] Record on Backend, Watch LiveTV on Frontend?

[John Kelley]

Why? It makes sense to have one central storage place for conifguration
information and what _little_ data anything needs stored. Having things
in multiple places (computers) will increase the number of questions
from people who are new to this; "Oh, now that I want to install
MythWeather || Myth* I have to install mysql on my frontend too?", "What
machine is the configuration for that stored on again?", ad inifinitum. 
You're barking up the wrong tree here. Also mythmusic *does* have a
backend, albeit it may not be the myth backend... It has to get its
files from somewhere.

	- John

-----Original Message-----
From: mythtv-users-bounces at snowman.net
[mailto:mythtv-users-bounces at snowman.net] On Behalf Of Joseph A. Caputo
Sent: Friday, April 11, 2003 11:14 AM
To: Discussion about mythtv
Subject: RE: [mythtv-users] Record on Backend, Watch LiveTV on Frontend?


This argument only holds for the monolithic mythfrontend app; what about
other 'frontend' modules like mythweather and mythmusic?  They require
database access & don't have any backend.  I think it might be overkill
to suggest that mythweather have a backend solely for database access.

-Joe C.

> -----Original Message-----
> From: mythtv-users-bounces at snowman.net 
> [mailto:mythtv-users-bounces at snowman.net]On Behalf Of Chris Palmer
> Sent: Thursday, April 10, 2003 11:34 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] Record on Backend, Watch LiveTV on 
> Frontend?
>
>
>
> would I be out-of-line to bring up the idea that the backends (and 
> maybe the master-backend) be the only machines that talk to the 
> database directly?  I can guess that there would be a bit of work 
> involved in making changes, so I'm not going to push hard on this, 
> unless I make time to help, but I'd like the idea out there at any 
> rate.
>
> I suppose one could argue about scaling issues with having all that 
> data flow thru a single host, but the database is also a bottleneck 
> for data flow, until multi-master cross-replication is released at 
> some future point for MySQL (someday, I think).
>
> I think it would simplify frontend setup, so that it doesn't directly 
> have multiple dependencies, nor require database libraries.  It might 
> be nicer for security, too, especially if Myth recognizes the concept 
> of a "user" at some point, which from the database structure, appears 
> like it might have been planned.
>
> -Chris

_______________________________________________
mythtv-users mailing list
mythtv-users at snowman.net
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users