Re: [infinispan-dev] Denormalizing hashes

2013-12-11 Thread Dan Berindei
On Wed, Dec 11, 2013 at 11:37 AM, Radim Vansa wrote: > > > On Wed, Dec 11, 2013 at 10:38 AM, Radim Vansa wrote: > >> Hi Dan >> >> I am not speaking about changing something for the C++ client, I >> understand that the client code cannot be changed in order to keep the >> backward compatibility.

Re: [infinispan-dev] Denormalizing hashes

2013-12-11 Thread Radim Vansa
On Wed, Dec 11, 2013 at 10:38 AM, Radim Vansa > wrote: Hi Dan I am not speaking about changing something for the C++ client, I understand that the client code cannot be changed in order to keep the backward compatibility. Sure, I was just trying to

Re: [infinispan-dev] Denormalizing hashes

2013-12-11 Thread Dan Berindei
On Wed, Dec 11, 2013 at 10:38 AM, Radim Vansa wrote: > Hi Dan > > I am not speaking about changing something for the C++ client, I > understand that the client code cannot be changed in order to keep the > backward compatibility. > Sure, I was just trying to give some background information on

Re: [infinispan-dev] Denormalizing hashes

2013-12-11 Thread Radim Vansa
Hi Dan I am not speaking about changing something for the C++ client, I understand that the client code cannot be changed in order to keep the backward compatibility. The current hash-wheel approach is working well, but there are few flaws that could be fixed keeping the client code untouche

Re: [infinispan-dev] Denormalizing hashes

2013-12-11 Thread Dan Berindei
Hi Radim Actually, it's me that wrote the denormalization code :) It was meant as a stop-gap measure before we upgraded the HotRod protocol to support the segment-based consistent hash, but the denormalization worked well enough (or so we thought) that we didn't get to changing the protocol yet.

[infinispan-dev] Denormalizing hashes

2013-12-10 Thread Radim Vansa
Hi Galder, as I am trying to debug some problem in C++ client, I was looking into the server code. And I am not sure whether I understand the code correctly, but it seems to me that the server denormalizes the consistent hash for each client anew (after each topology change or client joining).