From my point of view GTP has two primary virtues:
(a) ease of implementation (b) widespread support and interoperability Anything that undermines these two is unwelcome. If you need to do things that GTP doesn't (currently) do, (and i agree that there are many things that it doesn't do that a go protocol would in an ideal world), then a robust bi-directional bridge, released under a liberal license, seems like the logical choice for getting traction. Personally I'd love to see functionality improvements, including: * moving from file to generic URI references * interruption of "thinking" engines * moving beyond ASCII * handicap and ruleset negotiation I'd like to see implementation improvements including: * a validating filter (i.e. a program that sits between the engine and the controller and checks for conformance of both the engine and the controller to the protocol) * test suites for both engine and controller In an ideal world I'd love to see go move to RFC 3920, but that would be quite a disruptive shift. cheers stuart _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
