Protocol: Redesign Commands

[Yuffster]

It'd be a good idea to really think about the command set, since it doesn't have to be compatible with my old company's old protocol format.

So we whittle it down to the bare bones, say, just transfer. And (the cool part) enable some sort of macro mode in the YAML syntax to allow people to implement consolidate, distribute, mix, etc, then build up to even more complicated commands like dilute.

Of course, the more complicated commands will require me having beta users in a lab somewhere.

[Yuffster]

So commands should be first-class objects. That way they can have a method to print them out as a user-friendly string, normalize their own input, etc.

It also keeps Protocol and all the Handlers from having to duplicate work. For example, get_transfer_group can be a method on the base Command object.

We still end up with a method for every command on our objects, but I'm not sure of a way of resolving that situation.