refactor(epaxos.go) add comments for updateAttr and conflicts map

[xiang90]

@imoraru
I just begin to go through the codebase. Add some comments.
One question:
Is there any documentation about the checkpoint stuff? Is that only for clearing the dep map?
Can we just update the map after executing a command, like

id, ok:=dep[c.Key]
ifok&&id==c.Id {
delete(dep, c.Key)
}

[imoraru]

RIght now, the checkpointing thing is just for clearing the map, so that it doesn't get too big.
It's not safe to clear the map after executing on the local replica, because some remote replica may not have executed that command --- so it is necessary to be able to give that replica correct dependencies for subsequent commands. If, on the other hand, everyone says they have executed, it is safe to delete (but in Paxos you cannot assume that all replicas will respond, hence the checkpointing as a way to delete the map without everyone responding).

In general, I would say it's useful to look at the code, if you think it will help you understand the protocol better, but I would have started with the communication part first.

[xiang90]

@imoraru Sure. I will start with the communication part.

[xiang90]

@imoraru
Yea. You are right. Just to clarify the problem (since some of my friends will also read this).
I think there are three cases for the clearance of the deps map after execution:

1. the remote replica has also executed the command. There should not be any problem in this case.
2. the remote replica has received the command, but has not executed it yet(maybe committed or uncommitted).
   In this case, the remote replica will add the command into deps and send it back if there is an interference with that command. The command leader can make decision based on the situation.
3. the remote replica has not received the command.
   Both the remote replica and the command leader(who has executed the command) will not add the command into deps. But the command should be in the deps of the remote replica.
   In this case, there will be a problem that cannot be solved without other information (such as last received instance.id etc.)