Author: Dan Homan
Date: 12:46:28 09/17/98
Go up one level in this thread
On September 17, 1998 at 15:11:58, Dan Newman wrote: >On September 17, 1998 at 14:21:45, Robert Hyatt wrote: > >> >>I bend the rules here. You are supposed to make a move, offer a draw, and hit >>the clock. I do all *three* simultaneously... because I send a move, then I >>send "draw?" and hit the clock, and all three occur within microseconds of each >>other so that they are effectively done at the same instant. We could add a >>"press clock" command but that seems stupid. But it would fix the protocol as >>follows: >> >>move Nf7+ >>draw >>press clock >> >>In this protocol, I don't think it matters. Programs won't (I hope, and this >>could be an issue maybe) spew out a zillion "draw" offers while the other side >>is thinking. That *could* affect the other program obviously. ICC solves this >>for us, but the protocol wouldn't unless we address it. We could disallow draw >>offers without intervening "move xxx" commands to avoid any possible abuse? > >I agree about "press clock"; it would be there to solve only this one >problem and yet would be required after every move... Perhaps the interfaces >could be written to suppress multiple draw offers--so the hurt would only >be on the machine of the abuser. (This assumes all interface programmers >are pure of heart and mind of course.) > >-Dan. Why not simply have the interface only pass at most one draw offer following each move, subsequent draw offers are simply ignored by the interface? - Dan
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.