2009-12-28, 11:09
I wonder if the "server" will only require a MySQL database up and running (of which many NAS are capable of), or if it'll also need some other XBMC server software for real client/server communication etc. and a dedicated API.
I'm not sure if there could raise some issues if every XBMC client tries to play server and updates the db at the same time (maybe through automated folder rescans on startup etc.). So I think on the long run a "server version" of XBMC might be the best solution (imagine centralized skin and gui configuration for clients/accounts/usergroups etc.). Even client dependent local media shouldn't be a problem to be indexed server side, as you could use the UNC paths (\\my-client-pc\d$\local\folder\structure.mpg) and by this would even be possible to share the local media accross the other clients (assuming clients have access to that computer/share).
Once the unifiedPVR is ready, many of the users will have a dedicated TVserver with WOL anyway and some of us do already - so a XBMC server would be a great improvement I think and is the way to go in future. So maybe keep that in mind when restructuring the DB. What do you think?
I'm not sure if there could raise some issues if every XBMC client tries to play server and updates the db at the same time (maybe through automated folder rescans on startup etc.). So I think on the long run a "server version" of XBMC might be the best solution (imagine centralized skin and gui configuration for clients/accounts/usergroups etc.). Even client dependent local media shouldn't be a problem to be indexed server side, as you could use the UNC paths (\\my-client-pc\d$\local\folder\structure.mpg) and by this would even be possible to share the local media accross the other clients (assuming clients have access to that computer/share).
Once the unifiedPVR is ready, many of the users will have a dedicated TVserver with WOL anyway and some of us do already - so a XBMC server would be a great improvement I think and is the way to go in future. So maybe keep that in mind when restructuring the DB. What do you think?