Re: [computer-go] how to use GTP in place of GMP

[Don Dailey <drd@xxxxxxx>]

Hi Xavier,

The library  approach you talk about  is of course  the idea solution.
The thing  I'm curious about I  am not promoting as  a final solution,
it's more like a curiosity to me.   All that an API for such a library
needs is a read and write call and an initialization routine.  Then of
course the library COULD provide  multiple methods.  There are a bunch
of cool tools out  there that use GTP, so it would  make sense to make
sure a library supported these tools.

I'm no windows expert, but I assume there is a simple and easy way for
windows programs  on the same box  to communicate with  each other and
presumably this would be supported too, the easy windows way.

- Don





   Date: Thu, 12 Aug 2004 10:53:39 +0200
   From: Xavier Combelle <xcombelle@xxxxxxxxxxxxxxxxx>
   User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.4) Gecko/20030630
   X-Accept-Language: fr-fr, en-us, en
   Content-Type: text/plain; charset=ISO-8859-1; format=flowed
   X-Virus-Scanned: by AMaViS snapshot-20020222


   >I did  the UNIX remote  shell part  of the GTP  test and it  worked as
   >expected and only took 5 minutes to set up.
   >
   The important point is UNIX.

   >The TCP stuff  you guys are kicking around is a  good solution, but it
   >will be interesting to know if it can be solved without any additional
   >programming, whether  it's actually done or not  and without requiring
   >the GO programmer to worry about TCP stuff.
   >
   As explain later, the only way for not worry about any stuff
   is to chose a multiplatform way to communicate and to create a
   good library to use it. Gnugo has certainly something like that,
   if it could be released under LGPL, everybody should be happy.

   Avoid TCP stuff is only a way to limit the program to one
   kind of computer. Except TCP, I really don't know any portable
   way to communique with a program.
   But abviously, each patform as his "native" way to communique
   with the rest of the world without TCP.
   For Unix, it's remote shell, for java: RPC, for mainframe IBM: MQSeries, ...
   I think that the right way to  one platform is to use TCP/IP which is, 
   IMHO,
   was designed exactly for that purpose and implemented in all the 
   platform used
   to develop go programs.
   Of course, write TCP stuff is not too hard but however not trivial, so 
   that should
   be a good idea that if someone implement the way to wrap a native 
   communication
   with TCP for GTP it could be very interesting to give it for free.

   The talent of a go programmer is not to design the best way to communicate
   with the world but to communicate something interesting. So I really wonder
   why there is not general agreement about how to communicate. Just choose
   a multiplatform medium, implement it and everybody should be happy to 
   use it.
   Even a wrapper for GTP syntax parsing should be usefull.


   -- 
   Xavier
   It's not because it's easier for you that it's the same for evrybody.

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