Sent from my iPhone
On 14 Jun 2013, at 19:14, cotton-ben <[email protected]> wrote: > > /> Another thing you can do is have a replicated Cache holding the mapping > between the actual keys and the affinity keys./ > > Yes, no doubt about it. This will work. > > But, it technically requires the additional participation of a second > full-blown Cache. It will work, but it is not gorgeous. Giving me direct > API support for > > *K getKeyForAddress(Address pinnedNodeAddress, K objectNaturalKey);* > > is /gorgeous/ because it empowers me -- directly from the ISPN API -- to > not /necessarily/ carry around the additional participation of a second > full-blown Cache. As I've mentioned in the previous email, for your requirement, the only solution i can think of, *if* possible, has severe limitations when it comes to implementing it. Can you leave with this limitations? > > > > > > -- > View this message in context: > http://infinispan-developer-list.980875.n3.nabble.com/KeyAffinityService-nice-2-recommendations-tp4027152p4027405.html > Sent from the Infinispan Developer List mailing list archive at Nabble.com. > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
