I am not missing that point at all, it is what I thought I had been banging on about. I see the lack of a hardware part as a fatal defect.I read that discussion, and put what I judged the most useful of the URLs at
http://www.intelligentgo.org/en/computer-go/resources/specs.html. One of them
isn't working today. I read the others, and rather got the impression that
while people like the software part of GTP, they haven't got around to
inventing the hardware part yet.
I think you are still missing the point that there is no hardware part to invent here.
All you have to do is to set up a stream between controller and engine(s). See the section "Connecting kgsGtp to the GTP Engine" on http://intelligentgo.org/en/computer-go/servers/kgsGtp.html for four possible ways of doing this.
I put that page there, though I did not write any of it.
See Gunnar Farneback's "random go challenge" for a working setup to use GTP over the internet.
That is a good analogy. If I want to use the Dragon Go Server, I had better be, or become, familiar with how to use a web browser. If I want to use GTP, I had better become familiar with some other technology, but I have not yet figured out what.But I can see your point that we should somewhere have a short introduction to GTP where these problems are adressed. (But still it has as much to do with GTP as an introduction to using a web browser would have to do in an introduction to the Dragon Go Server.)