[mythtv-users] Proposed future power saving networked configuration (0.22 in mind)

Chris Pinkham cpinkham at bc2va.org
Thu Feb 19 02:39:10 UTC 2009


* On Wed Feb 18, 2009 at 02:52:01PM +0000, Mike Perkins wrote:
> I have often wondered whether or not there would be mileage in splitting 
> out the 'control' aspects of mythbackend from the tuner part, and 
> effectively making a 'mythcontrol' program that could run on a system 
> along with zero or one 'backend' modules (or perhaps one backend module 
> per tuner?). This module would do the scheduling, transcoding, etc and 
> have ownership of the database. I know some parts of the code have 
> already been broken out of the monolithic original... might there be a 
> future plan to make the whole system module-based, perhaps?

I don't see much reason in separating out the recording code from the
backend itself, especially if mythbackend is modified to fully support
a tuner-less master.  The main reason that things like mythcommflag and
the preview pixmap generation are executed externally is because there
have been times in the past when playback could cause a program to
crash.  We don't want a corrupt recording causing a crash during
'playback' (ie, flagging or preview generation) and taking down the
backend with it.  It was trivial for me to make a mythjobqueue app
because of the way the JobQueue is compartamentalized, and that was a
solution to running jobs on tuner-less servers.

--
Chris


More information about the mythtv-users mailing list