Re: [lily-dev] Client protocol

Deven T. Corzine (deven@ties.org)
Mon, 02 Dec 1996 09:13:11 -0500

>- You can already send beeps with no message - %g\n is perfectly
> legitimate and you'll find it at the beginning of every message.
> (Ok - this also must print a blank line. Granted.)

I don't really consider that blank line a negligible point, which is why I
said "without having to send a line of text with it." Sure, if you're going
to send a line anyhow, that's not a problem, but what if you weren't? The
lily-poker code sends a reminder message that takes up screen space, when I
would prefer to have a beep with no output. (Or maybe one reminder message,
then just beeps.)

>- The new server/client protocol has a signal built in. Changing the
> semantics of signaling, while I'd love it a lot, would break older
> clients while newer clients would have been expected to use the new
> protocol anyway.

Would these be signals based on particular events? I think there should also
be a way to do signals on their own as well...

Deven