Don Dailey drd@supertech.lcs.mit.edu writes:
This would be a useful command but the idea is to have a single standard (I think.) There is a lot of resistance to any kind of convienence feature, so I doubt this will go over well, even though I personally like it. It would be an easy way for a GTP based tool to quickly find out if the client implemented the standard set or at least enough for the tool to function.
Well, there is the precedent that, even though protocols like smtp or nntp are intended for program<->program, they provide help :
$ telnet localhost smtp Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 honda.isltd.insignia.com ESMTP Sendmail 8.9.3/8.9.3; Wed, 15 Aug 2001 18:36:18 +0100 help 214-This is Sendmail version 8.9.3 214-Topics: 214- HELO EHLO MAIL RCPT DATA 214- RSET NOOP QUIT HELP VRFY 214- EXPN VERB ETRN DSN 214-For more info use "HELP <topic>". 214-To report bugs in the implementation send email to 214- sendmail-bugs@sendmail.org. 214-For local information send email to Postmaster at your site. 214 End of HELP info help mail 214-MAIL FROM: <sender> [ <parameters> ] 214- Specifies the sender. Parameters are ESMTP extensions. 214- See "HELP DSN" for details. 214 End of HELP info quit 221 honda.isltd.insignia.com closing connection Connection closed by foreign host.
So given that gtp might be used interactively, list of commands could double up as help. Feels kind of wrong to standardise the format of the help output, though !
But would a gtp version number would be a better indicator of level of standard support ? Possibly worth tracking separately the comms protocol and the command set.
Don
From: "Phil" PhilippGarcia@home.com
I would like to propose a new GTP command: command_list. It that returns a list of all implemented commands (space delimited). For example:
< command_list
boardsize name protocol_version version black white genmove_black
genmove_white undo
This way the client can determine what GTP commands are available without having to attempt them.
Maybe one per line rather than space-separated list ? (Is there a maximum line length defined by the lowlevel part of the protocol ?)
dd