Raymond Wold wrote:
ivan dubois wrote:
It does use GTP.
I mean, why do you have to download a client to run locally? Why can't
you just use GTP directly against a socket?
I did not want to require people to change their program (adding
additional gtp commands) just to use CGOS.
- Don
There is at least one program that implemented CGOS protocol directly
into their program and does not need a client - they have the socket
protocol and the additional protocol needed that gtp doesn't support.
- Don
Jason House wrote:
On Sun, 2008-02-24 at 02:06 +, Raymond Wold wrote:
Raymond Wold wrote:
Don Dailey wrote:
Raymond Wold wrote:
ivan dubois wrote:
It does use GTP.
I mean, why do you have to download a client to run locally? Why can't
you just use GTP directly against a socket?
I did not want to require people to change their program (adding
additional
On Feb 23, 2008, at 7:51 PM, Jason House wrote:
I mean, why do you have to download a client to run locally? Why
can't
you just use GTP directly against a socket?
That's similar to what I did.
I implemented the CGOS protocol directly into my Go-programm.
It's very straight forward and I
On Feb 24, 2008, at 1:22 PM, Raymond Wold wrote:
Do you have any notes on what you found out about the protocol? Any
open source code?
I looked at the CGOS-client code (TCL script) and re-implemented it
in C, then I
linked that file to my Go-program. That makes it specific to my
program,
Don Dailey wrote:
No. cgos does not use GTP protocol for communicating with server.
Also, I have eventual plans to extend what is communicated to the
client and this is not compatible with the current GTP set.
The more you add as requirements on the client side, the more those bot
coders
On Feb 24, 2008, at 1:54 PM, Álvaro Begué wrote:
like the current scheme where a little program talks GTP to the
engine and then something else (I don't care what) to the server.
It would be better if the little client were written in Perl (there
used to be a Perl version but I don't know
