[mythtv-users] MythTV core structure.

[Joseph A. Caputo]

> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org
> [mailto:mythtv-users-bounces at mythtv.org]On Behalf Of Steele Price
> Sent: Thursday, August 14, 2003 2:59 PM
> To: Discussion about mythtv
> Subject: RE: [mythtv-users] MythTV core structure.
>
>
> I don't see how this makes you duplicate the functionality of any file
> system technology, it would just use those as they apply to MythTV, such
> as... frontend attaches to backend and all the file shares that go along
> with MythTV are here in this table instead of having to seek out what they
> are at a lower OS level, any changes made to the backend are immediately
> reflected to the frontend.  I personally am using autofs and nfs for this,
> but I still have to remember what the shared directories are on the server
> or create symlinks to all of them.  Someone else may choose to use samba,
> same scenario, you have to remember where everything is, this is of course
> not a big deal until you start duplicating it on more than one
> frontend.  If
> the front had a table of all shared directories for every module, I have
> them split across different partitions, audio on one, video on another,
> photos on a third and those may at some point all split onto different
> machines.
>
> Really, forking off a special branch to do this seems silly, but
> without TV
> as a module it makes it really difficult.

So now, not only would you introduce a dependency on NFS or Samba, but you'd
also like to make Myth be able to do NFS/Samba automatic client
configuration?  Sounds like a bit much.  I'd think it'd be much easier to
just extend the existing Myth backend resource serving (currently just
recorded program streams) to other file types, and update the plugin modules
to request files from the backend instead of directly through the file
system.  Isaac may not want to invest time in that, but he didn't say he
wouldn't accept patches.

-JAC