Global vs. Local Sage.properties

[freedml]

When I change a Sage.property, it only applies to that station. I always have to remember and take the time to make the same change to each tv, placeshifter, etc. When I forget to update one, it is irritating to the family that they don't all work the same way.

Solution: Basic functional property changes should have a dialog with choices like

"Apply change to all setups on this server?"
"Apply change to all Media extenders on this server?"
"Apply change to all Placeshifters on this server?"

[gplasky]

The sage.properties file only applies to SageTV when it runs as a server. Sageclient.properties file is used on PC clients and when the server is also used as a client. 000xxc53xxxx.properties (MAC address of the device is the name of the file)is used by HD100, HD200 and placeshifter.

For my extenders I just setup one and then copy and rename it to the clients directory. I remote desktop to the server or map a drive that directory and do it from a PC.

It sounds like a nice feature but I'm not sure how practical it is to implement. If the file is in use by an extender then the changes won't be written to the file.

Gerry

[GKusnick]

Originally Posted by freedml

Solution: Basic functional property changes should have a dialog with choices like...

I'm not sure exactly what you're proposing, but I certainly would not want to have an "Apply to all?" dialog pop up every time I fiddle with the sort order or filters on the recordings list. Nor would I want every options dialog cluttered with extra items to define the scope of the change.

The problem you're trying to address is real, but I don't think this is an appropriate solution. What I'd rather see is some sort of separate admin tool for setting up mirroring rules on a per-property basis (e.g. property X should be mirrored to clients A, B, and C). My feeling is that you'd want to set up these rules once and not have to tinker with them very often. Personally I could live without a GUI for this and would be happy to edit a text file (in .properties or .xml format, say) for setting up the rules.

That said, you'd want to be careful which properties you set up for mirroring and when the mirroring should actually be enforced. It would be weird to be browsing a recordings list and have it spontaneously re-sort or re-filter itself, or to have disk bars and other UI widgets popping in and out before your eyes because somebody at another client is fooling around.

Originally Posted by gplasky

It sounds like a nice feature but I'm not sure how practical it is to implement. If the file is in use by an extender then the changes won't be written to the file.

You'd need to enforce the property changes through the API rather than just overwriting the file, but there are existing tools for making remote API calls on a designated client.