[mythtv-users] MythWeb Access Help
Michael T. Dean
mtdean at thirdcontact.com
Fri Aug 10 16:20:45 UTC 2007
On 08/10/2007 08:08 AM, Mike Perkins wrote:
> Michael T. Dean wrote:
>> Even if there were a multi-user MythWeb patch available--without MythTV
>> multi-user support--it may help convince others to put some effort into
>> multi-user MythTV. MythWeb can always be changed to use the "future"
>> MythTV multi-user support once it's available.
> Mike, I am a little puzzled as to why Mythweb goes anywhere near Mythtv as such.
> When I browse the Mythweb pages, all of what I am seeing is data from the
> database. Is the php in the apache server leveraging some code in the associated
> back end?
Yep. MythWeb speaks Myth protocol to the backend (Myth's /network/
> I have for a while considered moving my mythtv database to another
> box, and running Mythweb on that box. If I can do that without having to install
> a dummy backend on it for the php to talk to, it obviously simplifies the
You can--as long as they can communicate over the network.
> What I'm getting at, perhaps, is that if Mythweb can be made to only talk to the
But then MythWeb would have to duplicate /all/ the logic in
mythbackend--even things like the scheduler logic (since the results of
such aren't really stored in the DB). While one person has claimed to
have rewritten all of MythTV in 40-some lines of Perl code, I tend to
believe it would take a bit more code than that (and, of course, since
MythWeb is PHP, it
> then different privileges for different users becomes purely an Apache
> configuration issue and multi-user Myth modifications can be made a separate,
> perhaps lower-priority, issue.
The main reason for doing the frontend/backend first is to ensure
consistent application of the access restrictions. But, it can be done
for MythWeb and then lessons learned used in the development for Myth,
then MythWeb modified to take advantage of the backend-provided
More information about the mythtv-users