Wed, 28 Mar 2001 20:29:57 +0100 (BST)
On Wed, 28 Mar 2001, Joris Robijn wrote:
> > the screen of this app is in front). In you scenario the admin has to
> > set up the exclusive key<->client in lcdd config and in the client
> > config to prevent the case where you have 4 knobs and every knob is
> > reserverd by an over client (every client thinks he can user the other 3
> > knobs if his screen is in front).
> Hmm I don't know. I'ld say no config of keys on the client side. If you
> don't specify this centrally, you might find all your keys getting
> stolen... (share-regulation is not enough)
I'm not sure that I was clear enough and you did understand the part of
"shared" correct so I will try to make clear that the "shared" is
"Send the keypress X to me regardless if it's registered by another
client because I do nothing with it what would influence with another
> That means that we have two opposit options now. Basically it is
> between (if i'm correct):
> 1. Let the server share out the available keys to clients, based on
> info in the config-file in the server-section.
> 2. Let the client-config tell a client he should get a key, and let the
> client reserve this key with the server. The server then needs to
> manage the key-sharing/reserving.
> Can other people tell what they think on this ?
Yes. Can somebody try to fix this deadlock, please .)
Andre' Breiler | Tel: +44 1737 839532
BBC Internet Services | Email: firstname.lastname@example.org
Kingswood Warren,Tadworth,Surrey,UK | URL: http://support.bbc.co.uk/
Mail me. Don't phone if possible. And use a Subject line.
To unsubscribe from this list send a blank message to