Now let's say mr. X decides that null-modem cable is the best way of communication in the world. He writes a set of scripts that allow to host a tournament on a set of computers connected by such cables. Another tournament provider, mr. B decides that those scripts are a masterpiece and hosts another GTP tournament. Now, we have two GTP tournaments, hosted with different communication channels used to transfer GTP sessions. * Do engine authors care? No, because tournament providers both accept programs speaking on stdin/stdout.
Of course they care, because someone should design a wrapper for stdin/stdout to null-modem cable. And write it is clearly harder than any TCP
* Do mr. A or mr. B care? No, because they both host working tournaments.
They don't need to intercommunicate with each other, because they have
two different tournaments there. They can easily switch from mr. X's
scripts to yours or vice versa.
That would be very strange to chose such a way. The LAN stuff is very cheap and no time of development. I don't understand why the would like to reinvent the wheel. After all IP means Internet protocol and Internert means Interconnected Networks. If you know something easier to use for communicating between windows, mac and unix, I am quite interested. Xavier _______________________________________________ computer-go mailing list computer-go@xxxxxxxxxxxxxxxxx http://www.computer-go.org/mailman/listinfo/computer-go/