Re: [infinispan-dev] rehashing hazard
Not only. We eventually want to have streaming state transfer implemented on lower-level
closer to JGroups callbacks and byte streams rather current higher-level serialization of
internal cache nodes. JGroups implements pull-state model and having both join and leave
follow that paradigm we can eventually just take out current higher-level transfer and
replace it with lower, more performant transfer. However, we have to wait for JGroups 3.0
to implement that.
On 2010-10-25, at 10:37 AM, Mircea Markus wrote:
>>
>
> Mircea, Have a look at the old LeaveTask.java. Pushing state on leave is complicated!
Hence InvertedLeaveTask.java which pulls state just like join task. We share a lot of code
with JoinTask, it is easier to maintain, comprehend etc etc.
I see. So the only reason to have both push and pull is code reuse?
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
Attachments:
- attachment.html (text/html — 2.2 KB)