Le mercredi 29 novembre 2006 21:02, Arvid Piehl Lauritsen Böttiger a écrit : > Hi. hi > > As a sparetime hobby project I've been thinking about makeing a > webbased go game, however, due to the complexity of go I'm not going > to write my own engine - and therefore I'm looking into gnugo good idea :)
> > I guess my main-problem is how I can make gnugo remember a state? I > may be wrong, but wouldn't the "best" (read "easy") way to solve this > problem just be to feed gnugo a state -> record the move -> terminate > gnugo -> give gnugos move to the user -> let the users make a move -> > feed the new state to gungo. This does however require a lot of new > processes, which indeed takes time, but to me it looks like a lot > cleaner solution that holding gnugo alive - or what do you think? why not keeping gnugo alive ? he uses cpu only when it thinks to its next move, and is very fast. > > Second - is there a good way to feed gnugo a state? gnugo -l mygame.sgf gnugo --help http://www.gnu.org/software/gnugo/gnugo_3.html#SEC25 > This is a hobby project only which > dosn't need to be able to handle 10.000 crazy go-geeks, hammering my > server, while playing go when they should be working :) > > cheers http://gnugo.jeudego.org/cgi-bin/gnugo looks like what you want to do. Happy going, cheers Alain _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
