Re: [Gnumed-devel] Gnumed-client ... ability to call another gnumed as slave

[Jim Busser]

On 16-Jul-09, at 8:53 AM, Karsten Hilbert wrote:

It is but doesn't pertain to the non-triviality I implied.

We do have the code - inside gm_ctl_client.py - so could

just reuse that. That part is fairly trivial. But -- which

slave personality would you want to connect to ? That'd have

to be decided somewhere. That is easy to solve - it just

needs a decision - but the actual content of the decision

can have implications reaching farther than immediately

obvious.

Maybe helpful to clarify the purpose and function of "personalities". Is it to distinguish among one or more instances of the slave running concurrently on a single local system? Can they co-exist on the same port? Do they all listen to the same incoming communications, but would each incoming communication (when properly framed by the controller) being directed to a specific personality therefore only acted on by the one personality?

Is a personality instance therefore

- a combination of a personality name

- specified where (config?)

- incorporated into (associated with) a gnumed client instance

- that has been instantiated as slave

- via port specified in (config?)

- using default worksplace (unless over-ridden in config)

And are personalities arbitrarily named by the users in their configs, or are the personalities to conform to particular personality types?

Does the server know anything about personalities (i.e. any risk of interaction among personalities in server space or middleware)?