INTERACT FORUM
Devices => Engen -- Home Automation with Z-Wave => Topic started by: glynor on February 05, 2016, 02:57:04 pm
-
I think JRiver's goal for the Linux version is to eventually enable people to use little pucks (and maybe "apps" on NAS devices) as servers. This requires some way to manage this stuff without remote desktop solutions, really.
-
We're working on the beginnings of remote management now.
The first small step is connecting the OneRemote app we've been working on with the Id settings. MC currently exposes its audio device setting. You can see this by typing in a browser:
http://[your IP address]:52199/WebRemote/
You could address your local copy of MC by typing this:
http://localhost:52199/WebRemote/
-
Without the ability to do "Full Control" from within MC itself, you're not going to have:
* Filesystem management (RMCF, essentially)
* File upload (for cover art purposes)
* View management
MC can already do all of that, so completely re-inventing the wheel seems... Silly. I recognize that some of that will take some extra elbow grease (particularly if the client and server aren't on the same OS platform). And, I think some view management (Theater? Media Network?) is actually stored in the Registry, even though they're considered part of the "Library".
Nevermind on that last bit. It works with my "trick" method.