[computer-go] GTPv3

[Ephrim Khong]

Don Dailey wrote:
>   1. controller sends async_genmove
>   2. controller (after some period of time) sends abort.
>   3. engine responds to aysnc_genmove
>   4. engine responds to the abort search

A effect might be that the engine has a gamestate where it's move has
taken place, while in the controllers state it hasn't. A general rule
would be that an aborted async_genmove (or any other async command that
changes anything withing the engine) requires a resync between the
controller and the engine.

eph