From: "Peter McKenzie" <peter_mckenzie@xxxxxxxxxxxxxxxxx>
[...]
As someone who is potentially the author of type 1 (smart) program, would I allow my program to be bombarded to a huge number of extra commands (all of which take non-trivial time for my program to process)? No way!Yes, you would. You're free to set about capturing all your opponent's dead stones, but if he wants a hundred or more agreement phases, then that's what you get, because reasonable precautions won't stop it.
Overall I could live with either protocol but I favour protocol A as I think it gives the best balance between features and simplicity. It happily handles the best case scenario (where both programs agree on score/dead stones) just as well as protocol B, but doesn't have the nasty worst case scenario of protocol B. Protocol A doesn't give programs a second chance to agree on score/dead stones but in practice I doubt that this is important - if they don't agree first time then I suspect it is likely they won't ever agree. And lastly, Protocol A involves fewer complications for the program authors to worry about.Agreed. Protocol C is interesting, but I prefer Protocol A's simplicity. Protocol B's unnecessary agreement shenanigans, I don't like. There's a reason that NZ and AGA rules, which were intended for humans, don't have multiple agreement either.
Anyways, I've probably said more than enough on this issue so I'll try to make this one my last post on it!!I will too, I hope.