Re: [computer-go] Protocol B

[drd@xxxxxxx]

> I would question whether Protocol B is any simpler than Protocol A, depends
> on how you look at it of course.

There is little difference.  Protocol B is slightly simpler for the server, 
they are the same protocol from the engine perspective, unless the programmer 
chooses to make some enhancements like you suggest in this post based on 
knowledge that we are using protocol B.

The only real difference (and this is more theoretical than practical) is that 
Protocol A for the server requires some exception coding.   Protocol B can be 
programmed in a very uniform way with no special cases.

> I'm not sure about lazy/exploitative behaviour but I do agree with Eric
> Boesch about the troublesome scenario that may easily arise. 

It nags at me too.   From an idealist point of view Protocol B is prettier and 
more uniform and it seems more correct,  but again this isn't really a 
practical issue.    

But on the other hand, protocol A is defeated by a single trivial disagreement 
that probably could be resolved very quickly.   Then we are back to not 
having any agreement other than pure play-out.

Don


_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/