I'm sure there are cases where an incorrect retry is bad, but for at least some use cases it is a trivial aspect of correctness and a worthwhile tradeoff in terms of app simplicity.
C On Jun 1, 2011 7:22 PM, "Ted Dunning" <[email protected]> wrote: > That is exactly the part of zkClient that I think is most subject to error > and is what I meant by inappropriate hiding of details. > > You can't just assume that you can retry an operation on Zookeeper and get > the right result. The correct handling is considerably more subtle. Hiding > that is not a good thing unless you say right up front that you are > compromising either expressivity (as does Kept Collections) or correctness > (as does zkClient). > > On Wed, Jun 1, 2011 at 2:05 PM, Jun Rao <[email protected]> wrote: > >> The most important feature that I rely zkclient on is to hide >> zkConnectionLoss exception (just block and retry when connection is in sync >> mode again). I assume that quite a few applications want something like >> that. Does it make sense for ZK to provide such functionality directly, >> instead of everyone implementing their own stuff? >>
