Originally posted by tmetzler
Point #1. I think you would have a greater chance of somebody complaining from entering in the wrong move, than from clicking on the squares. But really this is just a case of tough luck, but a hassle either way.
#2. How many moves do you guess are made on RHP every second? How many of those moves actually NEED to check for a "Next move" in the queue ...[text shortened]... ould surely add to the complexity of "simple tasks" like recording moves.
As someone pointed out, conditional moves are commonly used in postal chess. This is not an obscure feature.
As far as the move overhead, this could be implemented such that there is a new field attached to the game itself that is queried at the point the game's position is brought up that indicates whether or not there are conditional moves. This would require one additional field, not an additional query and would only require a query when additional moves are present. When additional moves are found, the overhead, I would suspect would be less than the overhead of a user actually logging in and making a move.
Hopefully the developers of RHP are making features scalable. If they go from 100,000 subscribers to 1,000,000 subscribers, it should not require any redesign, but merely adding horsepower behind the scenes.
This is a good site, but little features like conditional move and fast response time can make the difference in whether customers come and stay here verses going to competitors.