[infinispan-dev] DIST.retrieveFromRemoteSource

[Manik Surtani]

Doesn't setBlockForResults(false) mean that we're not waiting on a response, and can proceed to the next message to the next recipient?

On 27 Jan 2012, at 16:34, Dan Berindei wrote:

> Manik, Bela, I think we send the requests sequentially as well. In
> ReplicationTask.call:
> 
>               for (Address a : targets) {
>                  NotifyingFuture<Object> f =
> sendMessageWithFuture(constructMessage(buf, a), opts);
>                  futureCollator.watchFuture(f, a);
>               }
> 
> 
> In MessageDispatcher.sendMessageWithFuture:
> 
>        UnicastRequest<T> req=new UnicastRequest<T>(msg, corr, dest, options);
>        req.setBlockForResults(false);
>        req.execute();
> 
> 
> Did we use to send each request on a separate thread?
> 
> 
> Cheers
> Dan
> 
> 
> On Fri, Jan 27, 2012 at 1:21 PM, Bela Ban <bban at redhat.com> wrote:
>> yes.
>> 
>> On 1/27/12 12:13 PM, Manik Surtani wrote:
>>> 
>>> On 25 Jan 2012, at 09:42, Bela Ban wrote:
>>> 
>>>> No, parallel unicasts will be faster, as an anycast to A,B,C sends the
>>>> unicasts sequentially
>>> 
>>> Is this still the case in JG 3.x?
>> 
>> 
>> --
>> Bela Ban
>> Lead JGroups (http://www.jgroups.org)
>> JBoss / Red Hat
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org