Yeah, I'm slightly sceptical of this logic given that it relies on a knowledge of the underlying ping timings used by the ZooKeeper client implementation.
Thanks for providing this library by the way, it's proving infinitely easier than using raw ZooKeeper client connections. cheers On Wed, Oct 9, 2013 at 8:16 AM, Jordan Zimmerman <[email protected] > wrote: > I think that's generally safe, but I'd be nervous about time based > assumptions like that. In the recipes I write I always err on the side of > caution. > > -JZ > > On Oct 8, 2013, at 2:13 PM, Cameron McKenzie <[email protected]> > wrote: > > My thinking was that for cases like a standard Mutex lock that can only be > held by a single client at a time, it can assume that it still holds the > lock after it sees a SUSPEND event until 2/3 of the session timeout has > expired and it hasn't reconnected. > > >
