How is Paxos implemented in doozer

[Prat]

Can anyone explain how Paxos is implemented in doozer? Suppose a message is added by a client on a particular server. what are the sequence of steps followed by paxos?
what happens when a value is chosen? When will the values stored by the acceptors be reset? else wont the proposer keep proposing the last accepted value forever?

Thanks.

[Brandon Philips]

Hello Prat-

If you are looking for a system like Paxos-like library I would suggest you check out the raft library in etcd: http://godoc.org/github.com/coreos/etcd/raft

It has been adopted by a couple of other projects besied etcd including: CockroachDB and beehive.

Cheers,

Brandon