Don wrote:
I think there are about 4 commands that should be included in any protocol no matter what. Why can't the rest be up to the go engine programmers to implement? We can define a reasonable set of very useful commands and you can just return "not_implemented" if your engine cannot deal with this. I can't see why this should be viewed as unreasonable.
Consider:
- 'unmove'. Big deal. Don't implement it. You can still use
the Gee Whiz super duper interface and it just says "Sorry, this command unsupported by engine." No big deal.
[Snipped.]
Enough. You are repeating yourself. We don't need any more recapitulations of these arguments.
/Gunnar