Re: computer-go: Go Protocols

[Dinghao Wu <dinghao@xxxxxxxxxxxxxxxx>]

Yes, I totally agree with you. Go Modem Protocol is not simple enough and
not in high level. We have better low-level networking protocols such as
TCP/IP. Why do we need another so low-level Go Modem Protocol? We can
build Go communication protocol in higher level based on the low-level
network protocols. For example, we can build it using Socket. It'll much
easier to understand and write go program.

The communications between two computer go programs and between go server
and go client essentially do not have much difference from a high-level
point of view. Thus, our high-level go protocol can fit to any purpose.

Dinghao Wu
http://www.cs.princeton.edu/~dinghao/

> This in mind, I wonder if there are better protocols out there.
> Properties I'd wish for a protocol are:
>
> Server based  (Server starts and controles the engine(s)).
> Ascii         (Easier to debug for humans, will give the chance of
>                simulating an engine via telnet or stdin/stout)
> Simple        (Why making complicated when not needed.)
> Extendable    (If possible I'd like to start special features of the
>                engine from the server rather than interact with the
>                engine directly)
>
> Do you know any, that suits this (or part of this)? I've seen, that
> gnuchess uses a protocol, that looks like something I'd use (but
> that's for chess ;-).
>
> Thanks, Berni
> +------------------------------------------------------------------------+
> | Bernhard Seckinger, University of Freiburg, Computer Science Institute |
> | Am Flughafen 17, Gebaeude 51, 79085 Freiburg, Tel.: +49-761-203-8165   |
> | E-Mail     : seckinge@xxxxxxxxxxxxxxxxx                       |
> | WWW        : http://ad.informatik.uni-freiburg.de/~seckinger           |
> +------------------------------------------------------------------------+
>