home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Client / Database connectivity - Why?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MrTechno" data-source="post: 959024" data-attributes="member: 111518"><p>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.</p><p> </p><p>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"?</p></blockquote><p></p>
[QUOTE="MrTechno, post: 959024, member: 111518"] 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"? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Client / Database connectivity - Why?
Contact us
RSS
Top
Bottom
