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

[Don Dailey <drd@xxxxxxx>]

And  by  the way,  I  agree with  William.   GTP  doesn't dictate  the
communication  channel or  method,  I don't  see  why this  limitation
should  be imposed.   It's  very  useful and  flexible  that you  have
multiple  communication channels avaialable.   That's a  limitation of
GMP, not a selling point.

For instance,  how do  I hook  two GMP programs  together with  only 1
computer and one serial port avaiable  if that's what I want to do?  I
don't, unless there  is some hack, but it would  have to be considered
"non-standard" to GMP.

A  library  could  provide  any   number  of  possible  methods  as  a
convenience.

- Don



   Date: Wed, 11 Aug 2004 11:21:16 -0400
   X-Authentication-Warning: nene.csail.mit.edu: drd set sender to drd@xxxxxxxxxxxxxxxxx using -f
   From: Don Dailey <drd@xxxxxxxxxxxxxxxxx>
   CC: computer-go@xxxxxxxxxxxxxxxxx
   Reply-to: drd@xxxxxxxxxxxxxxxxx


   Probably, what is missing is a  useful library to interface it to your
   program.  I  just made  another post  where I said  the library  was a
   simple as  the interface to the  library itself, but  this is probably
   not exactly  true, a  library could  take a little  of the  pain away,
   especially for Windows users.

   Plus, a library could  provide multiple communication methods, such as
   the  GTP/TCP you suggest, STDIO, SERIAL,  etc.

   - Don




      From: "yonik" <yseeley@xxxxxxxxxxxxxxxxx>
      Date: Wed, 11 Aug 2004 10:25:45 -0400

      > 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/

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