Don Dailey wrote:
Raymond Wold wrote:
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 who can't or don't want to run third party interface code will
have to implement.
Exactly, and that is why I don't require anything other than GTP to
run a bot on CGOS.
But you do; you require a custom protocol. The fact that you've provided
code that implements this protocol and interpret to GTP doesn't change
that; not everyone will be able to or will want to run this code.
Don Dailey wrote:
It would be so much simpler if everyone used GTP directly on the
server. I am aware that GTP lacks authentication features, but it
should be simple enough to agree on a command and say that that's now
the standard.
I am quite sure that would raise the entry barrier too high - many
programs would not run on CGOS if I did this.
They don't have to actually implement the extra GTP commands you know,
you could provide client code that handles that for them just like you
do today, thus making the job for those who have to code the
interface code themselves much easier. You could even keep your custom
protocol on the side without troubles.
Besides, I resever the right to extend the protocol when I enhance the
server later - this would require each person to rewrite their program
each time I decided to make a change. That's not acceptable.
Make all extra client capabilities optional, used only if list_commands
includes them, and it won't be a problem.
When you extend the protocol now, some people will already have to
rewrite their program, because they've ported your tcl script to their
own system.
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
