Re: [infinispan-dev] Design of Remote Hot Rod events

On Nov 19, 2013, at 2:49 AM, Mircea Markus <mmarkus(a)redhat.com&gt; wrote: There's a difference between an update and a delete. The update can carry the latest version of the entry in memory, which could be of use to the client, if for example they want to do a replace() as long as the version has not changed. The delete would not have that info since the entry is gone. I think it's more logical to have both separate. Well spotted :). There are two ways to solve this. First one is by adding the source id to each cache operation sent from the client. This would require a change in the way the header is parsed for all operations. This is the simplest solution, with a little addition to the header. The second option is a bit more complicated but avoids the need to send the source id per request. At least in the Java client, each connection opened sends a ping at the start. You could add source id to the ping command, and then the server could track all incoming connections that send a particular id. There could be multiple in the case of clients pooling connections. The server can track disconnections and keep this collection up to date, but it'd be quite a bit of work on top of the rest of stuff. I'd prefer the first option. Cheers, -- Galder Zamarreño galder(a)redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org