Figure out enabling/disabling modules without restarting manually

[astrobokonon]

Ideally, this would be fairly transparent and all happen thru the broker. BUT, that means that whomever/whichever client issues the commands needs to know about the active modules that Mr. Freeze has, either because they're all hardcoded or because they're advertised. If it's the former, I wonder just why I have a configuration file in the first place. Seems like it should be the latter - Mr. Freeze/Nora should advertise their active modules once every XX seconds and anyone can listen/discover them.

Should I allow arbitrary injection of whole new modules? Seems possible, but might not be a good idea. The command-issuer necessarily must have some knowledge of what the format should be, but the more I think about this the more I realize that having a hardcoded configuration file is a bit of a breaking

[astrobokonon]

This is all especially important during these warm up/cool downs/removals. It'd be a big PITA if I had to change the config manually each time, this seems like it should be a major component of the user interface.

[astrobokonon]

First task: reorganize the parsed configuration to be per-instrument rather than per-device. Having things per-instrument will be easier/faster for logging as well.

[astrobokonon]

This also means determining the exact structure of the command packet. There's a lot wrapped up in this single issue.

[astrobokonon]

RE: the above, see #8

[astrobokonon]

I think this issue is good to close, since it's really wrapped up in the other issue. Closing.