Re: Patch for two issues

[Brian W. <bwe...@xb...>]

On Jul 22, 2010, at 10:30 AM, Kocik, William wrote:

> In this case, I’ve clearly misunderstood the purpose of sendAsync(). I was using it to send NOTIFY messages to a group of slave name servers, and when it was discovered that it was only sending to the first name server on the list, this was the “fix” I implemented.
> 
> Is there some built-in mechanism to send a message to a bunch of name servers (synchronously, now that I think of it) or should I thread that on my own?

There is no method for sending a message to multiple servers, and I'm not sure how that would even work in a general way.  When dealing with multiple messages, there are a number of different ways to handle errors, and the correct one will generally be application-specific.

Brian

> On 7/22/10 1:18 PM, "Brian Wellington" <bwe...@xb...> wrote:
> 
> ExtendedResolver.java – sendAsync() was not using its multiple resolvers to send a message, only the first one on the array.
> This is the intended behavior.  Multiple requests will be sent if necessary (that is, if the first request fails or times out), but in the normal case, a single request sent using the first resolver (or a random resolver if setLoadBalance() has been called) is sufficient.
> 
> Brian
> 
> 
> 
> 
> 
> -- 
> Bill 
>