3.0.1.....
my watches get recreated on the new server but I'm still too aware of
connections.

In fact, shouldn't disconnect be removed entirely?  Or is this just advice
telling the client that something bad might have happened?

Kevin

On Tue, Jan 6, 2009 at 7:12 PM, Mahadev Konar <maha...@yahoo-inc.com> wrote:

> http://issues.apache.org/jira/browse/ZOOKEEPER-23
>
> This has been fixed in zookeeper-3.0 release. Are you using a release from
> sourceforge?
>
>
> mahadev
>
>
> On 1/6/09 4:57 PM, "Kevin Burton" <bur...@spinn3r.com> wrote:
>
> > This could be simplified if the semantics for reconnect were simplified.
> > Is there any reason why I should know about a disconnect if ZK is just
> going
> > to reconnect me to another server in 1ms?
> >
> > Why not hide *all* of this form the user and have the client re-issue
> > watches on reconnect and hold off on throwing exceptions if the server
> > returns.
> >
> > This would allow the user to just handle three conditions... total
> ensemble
> > failure, no ACL permission, or no node existing (of vice-versa).
> >
> > Kevin
> >
> >
> >> If I run an async request, the client should replay these if I'm
> >> reconnected to another host.
> >>
> >> --
> > Founder/CEO Spinn3r.com
> > Location: San Francisco, CA
> > AIM/YIM: sfburtonator
> > Skype: burtonator
> > Work: http://spinn3r.com
>
>


-- 
Founder/CEO Spinn3r.com
Location: San Francisco, CA
AIM/YIM: sfburtonator
Skype: burtonator
Work: http://spinn3r.com

Reply via email to