[mythtv-users] Record on Backend, Watch LiveTV on Frontend?
Chris Palmer
mythtv at zencow.com
Fri Apr 11 03:33:37 UTC 2003
Bruce Markey wrote
> Chris Palmer wrote:
> > Isaac Richards wrote
> ...
> >>You're not supposed to run the setup program -- it's for backends only. the
> >>Master server address is a global setting, and only needs to be set up once.
> >>All a frontend needs in the way of setup is mysql.txt pointing to the
> >>database, then everything can just be customized as normal from within the
> >>frontend settings.
> >
> >
> > oh neat. is that new? I thought I had to tell the frontend which master
> > backend to use by using that config. :)
>
> The frontend finds this in the settings table. All the info
> the frontend needs is in the database. It only needs the
> backend when it requests an available tuner for live TV,
> reports a schedule change or, of course, requests a file to
> playback. However, a couple other things are requested from
> the backend like the delete list where the files sizes are
> added.
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
More information about the mythtv-users
mailing list