Re: [computer-go] GTP and Tourney in SmartGo 1.4

[Xavier Combelle <xcombelle@xxxxxxxxxx>]

Hello,

I'm a new member of  computer-go mailing list,
but I have an idea about the following problem.

>  How about GTP/TCP for the
> specification of how to put GTP over TCP sockets? 
So I make the following proposition.

IMHO the specification of GTP over TCP socket can be simple from GTP 
specification:

To implement GTP, a go engine MUST be able to open a client socket
(default address/port is 127.0.0.1:50715, SHOULD be parameterizable).
A go controller MUST be able to open a TCP Server
(default address/port is 127.0.0.1:50715, SHOULD be parameterizable).

As an extension a go engine CAN be act as a TCP server
and the go controller CAN act as a TCP client.
This last case can be very useful to connect two servers.

The single hard point maybe if there is the deconnection.
But it the behavior is a controller decision. (A clever
behavior may be at the reconnect reload the game
as it was before deconnection)

The reason why I propose that the engine is by default
the client and the  controller the server is to make the
design of new engine easier. Of course, implement
the server behavior is not so hard, so that should
be a good decision to let the conception of a new
controller easy.

Of course, I'm not an expert in computer-go problems,
so I let you correct this draft.

Xavier


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