[LAD] OSC: Divide & Conquer, or build a Stronghold?

Hey all, I've been keeping myself busy lately, mostly with Python and OSC, and I'm using multiple clients/controllers to send messages to a sampler with an OSC interface. place where all Audio programs "Announce" thier OSC port & program name & version, so the linux-audio-desktop can be a little more "coherent" for lack of a better word.. ;-) We could create a kind of "Master OSC Host" which would keep track of which clients are running, and which ports they are using. This would be easiest to do if EACH client, would "register" itself on an agreed port. So if a client wants to read some information, they could query the "Master OSC Host" with a standardised set of questions about the current state of QTractor/Ardour/<Any OSC capable program>. This would mean that any program that wants to find out which Jack B:B:T or Frame were on or if there's been XRuns, wouldnt have to be a JACK client, because its been abstracted to the "Master OSC Host". I think this method would allow better inter program operability, as any "useful" information that one program could share, other could read. This would be most effective, if we also requested that programs followed a specific naming convention for features that each program has. EG: Save : /<prog_name>/save_state Load: /<prog_name>/load_state etc I'd like to get the communities feelings towards an initiative like this, feedback/criticism/opinions welcomed! -Harry Haaren