And unrelated:
- I've sometimes wanted to see who is currently playing on the
server. Will this be possible (e.g. through a web pages that gets
updated every few minutes)?
The web page will be in PHP, so when you refresh the web page you
will get the exact and current state of the server. In other words
if I log on and 2 seconds later you hit the site, you will see that I
am logged on.
That would be great. Definitely good enough for me.
I am also considering the idea of sending info message to every client
when someone logs on or off and perhaps even to broadcast the result
and pairings of each game.
What do you think of that? If I do that, then a sophisticated enough
client could track the state of the server without requiring the user
to constantly refer to a separate web page. Of course this does not
change the protocol since "info" is already defined as part of the
protocol, although to be most useful I would have to standardize the
exact format of those kinds of messages.
I personally have no requirement for that. I can put it in the client if
somebody else wants it. I actually considered parsing the current "next
round" info messages, but decided against it. I did not want to create a
bad dependency, and I think I would continue to treat info messages as
unparsed text.
I would probably steer clear of putting this in the protocol, as it may
contribute to lag. Also, if somebody writes a badly engineered client
that reconnects too quickly, all current players would get flooded with
updates.
Christian
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/
