Petr, I would love to see a fully HTTP protocol based JSON server based using asynchronous messaging. Contrary to some of the "I love to parse characters and want as efficient as I possibly can down to doing bit twiddling encoding/decoding on input/output even if it is no where NEAR the bottleneck damn the humans and their ridiculous need to have things be readable", I think generating a robust middleware server architecture would be quite nice. It would allow for quite a few additional features (GUIs, logs, DB reports, full game saves, trivial .sgf exports, etc.) a very low implementation costs, especially if originated in something like Java or C# where the middleware libraries and DB connectivity is super-abundant.
And then for those who insist, the ability to write small adapters which translate GTP into and out of the JSON protocol ought to be trivial, including making language specific libraries to do so. The bottleneck is in each of the clients attempting to work on their specific move, not on the server who spends the bulk of it's time twiddling its thumbs waiting for a client to finally make a move. Jim O'Flaherty ________________________________ From: Petr Baudis <[email protected]> To: [email protected] Sent: Mon, May 16, 2011 3:14:19 PM Subject: Re: [Computer-go] New Go Protocol for the web On Mon, May 16, 2011 at 11:51:27AM -0400, Don Dailey wrote: > On Mon, May 16, 2011 at 11:11 AM, Petr Baudis <[email protected]> wrote: > > Also, it makes > > assumptions about one side being a go robot. > > > That is not an assumption, it's what it's designed for. That is like > saying your vehicle is designed with the assumption that a human being is > going to drive it. Yes of course it is, that's who it is designed for. But I'm not saying that GTP is wrong or needs to be replaced (well, sometimes I do feel constrained, but that's entirely different matter). We are just talking about a different scenario here, one where much larger amount and more complex structure of data than "next move" may need to be funneled, one that works in a fundamentally asynchronous environment and where one of the sides is going to be a web client. -- Petr "Pasky" Baudis UNIX is user friendly, it's just picky about who its friends are. _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
_______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
