[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [computer-go] How to play go with other programe?



> Nobody ever said that. The point is that the tournament organizer
> can decide it as it suits him, and I see no point in specifying this in
> the GTP specification.

Standards are useful.  A (at least one) transport should be specified, but
it's pedantic arguing if the specification should be part of the GTP spec
proper, or an add-on.

Think about the relationship to HTML and HTTP.  What made the web *really*
useful was the standardization of both of them.  Imagine if only HTML were
standardized and you had to figure out your own way of getting the documents
from each web site you wanted to look at!

Having the GTP spec be transport agnostic is fine, as long as other
standards do define transports.  I have advocated the name of GTP/TCP to
describe how Go programs should talk GTP over TCP (ports, who opens, maybe a
URL format specification, session level stuff like reestablishing broken
connections, etc).

Then, if someone wants to run a tournament, the specifications could be
pretty simple, all that is left to specify is the physical connection.
Example: "Protocol will be GTP/TCP, physical layers available: 10BT, 100BT".

-Yonik

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