Except this method, have any onther method to control the authority of zk? ---- nileader ni掌柜的个人邮件. Email/MSN：[email protected]
*这里一封来自ni掌柜个人邮箱的邮件.如果你觉得邮件内容中包含任何关于个人隐私的信息,请勿转发.谢谢.* 2011/10/20 Fournier, Camille F. <[email protected]> > You will receive an exception of NoAuth in the event thread. The addAuth > call is not synchronous, so you can't just expect an addAuth call that > succeeds to actually have succeeded without verification that the connection > is still valid after that call. Anyway, it's not that tricky, just not as > straightforward as some of the other things. > > C > > -----Original Message----- > From: nileader [mailto:[email protected]] > Sent: Wednesday, October 19, 2011 7:58 PM > To: [email protected] > Subject: Re: Something about zkclient > > Nice to hear from you. C. > > > So, why tricky. In zk's original api, if you add an error authInfo, then > you > will receive en exception of NoAuth. Then user's operation will be fail. > > > ---- > nileader ni掌柜的个人邮件. > Email/MSN：[email protected] > > *这里一封来自ni掌柜个人邮箱的邮件.如果你觉得邮件内容中包含任何关于个人隐私的信息,请勿转发.谢谢.* > > > > 2011/10/19 Camille Fournier <[email protected]> > > > The author never implemented it, you'll have to modify the source and add > > it > > yourself. It's a bit tricky because the call will always succeed > > immediately > > even if the auth actually fails, I recommend doing a simple synchronou > > exists call immediately after to force the error to flush through if > there > > is one. > > > > C > > > > From my phone > > On Oct 18, 2011 10:23 PM, "nileader" <[email protected]> wrote: > > > > > hi, everyone. > > > Any one who use https://github.com/sgroschupf/zkclient this. > > > > > > In zk original api, there is api: zk.addAuthInfo(authentication_ > > > type, correctAuthentication.getBytes()); > > > > > > but in https://github.com/sgroschupf/zkclient, no. > > > > > > who can tell me why? > > > or who know the author of the zkclient. > > > > > >
