Re: [infinispan-dev] Hot Rod - pt2

> Hmmmm, those two sentences seem to contradict each other. When there's a full cluster restart, and your sockets gets "closed by peer" and you can't contact any of the remaining servers, next time I think it's better if you send -1 rather than trying to send the old view. Otherwise, you might have issues like this: - Client had vClient=2. - Cluster restarts and after two hot rod cluster nodes started up, vServer is 2. - Client figured out that the cluster restarted and restablishes the contact and sends vClient=2. - The server does not send an updated view. Now, this would be a problem for example if while the server was down, you had changed the TCP port where the hot rod server was listening, or there was some other change that might have affected the calculation of the cluster node hashcode. If the client sends -1, you avoid this issues, it's like a local reset.