Re: computer-go: Go Protocols

[Nick Wedd <Nick@xxxxxxxxxxxxx>]

seckinge@xxxxxxxxxxxxxxxxx writes

>I'm relatively new to computer go (and go as well) and just started to
>write an engine. Now the question of what protocol to use. I know two,
>that both I'm not happy with:
>
>a) Go Modem Protocol 
>I've translated the gmp.c to java and it works (more or less), I can
>connect to cgoban. But my implementation seems somewhat unstable. I
>inserted some debug-code. With debug-code it works, but I have an odd
>feeling (something with timing seems to be wrong). Also I'd prefer to
>setup my engine via the protocol, which isn't possible. With cgoban I
>can't even test the undo-feature. An other drawback is, that it isn't
>ascii based.

You seem to be saying that there is a bug in your implementation of the
protocol.  That is not a criticism of the protocol itself.

There is a specification of the Go Modem Protocol at
    http://www.britgo.org/tech/gmp.html

>b) NNGS/IGS-Protocol
>I havn't internet connection at home, so I'd need my own server what I
>think isn't worth the work. I havn't found any description of the
>protocol, too.

These two protocols were designed for different purposes.  The Go Modem
Protocol is intended to allow two computer Go programs to play each
other using a serial link.  The NNGS/IGS-protocol is intended to connect
a Go client to a Go server over the internet.

>An other drawback of both of them is, that they aren't simple to use.
>So I thought of creating my own protocol, but that has the drawback
>that it will not used widely. 

What do you intend using your protocol for?

Nick
-- 
Nick Wedd    nick@xxxxxxxxxxxxxxxxx