Re: [computer-go] GTP and Tourney in SmartGo 1.4

["Yonik Seeley" <yseeley@xxxxxxxxxxxxxxx>]

> Of course.  We know that.   That's exactly what I'm saying.  The linux
> folks already solved  this problem but we haven't  decided how to make
> this work well with Windows.

This is getting silly.  This has nothing to do with Windows vs Linux... both
operating systems have roughly the same capabilities when it comes to
IPC mechanisms.

> Right now, with NO additional  programming, I can connect 2 pipe based
> GTP go program running on  their OWN computers using twogtp.pl.

I don't see how that's possible without some kind of network protocol.
pipes isn't
going to get you from one computer to another.  Did these systems share a
filesystem
(such as NFS) in which info was passed?  If so, this isn't a general
solution.

> The beauty  of linux is that  twogtp.pl probably was  written with the
> intention of running  2 programs on the same  computer, but it doesn't
> really  matter if  the  2 program  are  on different  machines on  the
> network,  it  just  works  remotely too.   No  additional  programming
> required.

That would only be true if it uses TCP sockets or some other network
protocol.
It doesn't as far as I can see.  Perhaps you have a version that someone
hacked
to use sockets?

> The  problem  we  are trying  to  solve  is  how to  overcome  Windows
> limitations in this regard and  I think the basic solution has already
> been proposed:  Use TCP sockets.

What limitation is this?  Windows can do pipes, sockets, shared memory,
etc...
I'm a UNIX guy myself, but I have occasion to develop on Windows also.
If you want the exact UNIX APIs on Windows, that is also doable via free
cygwin or SFU, but that's just an implementation detail.

Oh, and if twogtp.pl works on UNIX, it should also be able to work on
Windows under cygwin or SFU (or maybe even without).

The only thing that needs to be done is to standardize GTP/TCP!
A Go developer would then have many options:
1) directly implement the GTP/TCP protocol (open sockets, read/write GTP to
it)
2) read/write GTP to/from stdin & stdout and have a helper program that
redirects over a socket
3) connect an existing GMP program to a helper program that translates to
GTP/TCP
4) etc

The bottom line is that the implementation details aren't important... they
can easily
be done for every OS in use now... the important part is standardizing the
protocol.

-Yonik

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