United Kingdom
Recently I made my single-seat setup into a multi-seat setup and was having problems with the client-only machine locking on using the "Recorded TV" function. After a bit of FAQ / forum searching and some trial an error I realised the problem was the TV Client machine couldn't access the MySQL database.
A additional firewall rule fixed so my immediate problem is solved, but my question is why does the TV Client need access to the database at all? Paths to the recordings stored in the database are local to the TV Server machine; they can't be accessed that way so the TV Server must be streaming them. Why go to the trouble of implementing that and not do the data access that way as well? Was it simply a case of "letting the TV client connect to the database requires less effort than exposing it through TV Server"?
A additional firewall rule fixed so my immediate problem is solved, but my question is why does the TV Client need access to the database at all? Paths to the recordings stored in the database are local to the TV Server machine; they can't be accessed that way so the TV Server must be streaming them. Why go to the trouble of implementing that and not do the data access that way as well? Was it simply a case of "letting the TV client connect to the database requires less effort than exposing it through TV Server"?