The other thread was already quite big and covering a large range of
issues so thought I'd spin up a little separate thread :)
I've just updated the patch to include better javadoc which is linked
to an embedded HTML documentation describing the protocol. The
documention includes the pseudocode
The other thread was already quite big and covering a large range of
issues so thought I'd spin up a little separate thread :)
I've just updated the patch to include better javadoc which is linked
to an embedded HTML documentation describing the protocol. The
documention includes the pseudocode
Hi James, the fact that the client's node has another node n ahead of it the
in the sequence order doesn't mean that the owner of n is aware that it is
the lock holder or the leader. This is because operations are propagated
asynchronously. Also, a getChildren() doesn't guarantee that you have the
Thanks for the clarification. I think it makes lots of sense for the
leader to write to some canonical place to advertise itself; if others
are interested in knowing if it is the leader
2008/7/18 Flavio Junqueira [EMAIL PROTECTED]:
Hi James, the fact that the client's node has another node n
