Yes, it watches the bogus node but it also blocks until the second ZK instance successfully connects. I found that both of these things are necessary for reliable session killing.
-JZ On Aug 21, 2012, at 2:30 PM, Ben Bangert <[email protected]> wrote: > Ah, perhaps I'm misreading the Java code. It looks like it operates in the > FAQ manner except it adds a watch for a non-existent node so that it can > register a watcher for when it gets the next event... which is *assumed* to > be a session being lost.
