Conceptually I like the grouping API better than AtomicMap as I don’t have to
rely on a specific Infinispan type.
We do use FineGrainedAtomicMap both for the entity and the association
persistence (not AtomicMap). It is particularly critical for how we store the
association navigation
On Jan 22, 2014, at 1:26 PM, Emmanuel Bernard emman...@hibernate.org wrote:
Conceptually I like the grouping API better than AtomicMap as I don’t have to
rely on a specific Infinispan type.
We do use FineGrainedAtomicMap both for the entity and the association
persistence (not
On Tue, Jan 21, 2014 at 4:07 PM, Mircea Markus mmar...@redhat.com wrote:
Hi Emmanuel,
Just had a good chat with Davide on this and one solution to overcome the
shortcoming you mentioned in the above email would be to enhance the hotrod
client to support grouping:
RemoteClient.put(G g, K k,
On 22 Jan 2014, at 14:48, Mircea Markus mmar...@redhat.com wrote:
On Jan 22, 2014, at 1:26 PM, Emmanuel Bernard emman...@hibernate.org wrote:
Conceptually I like the grouping API better than AtomicMap as I don’t have
to rely on a specific Infinispan type.
We do use
On 01/22/2014 01:58 PM, Dan Berindei wrote:
It would also require us to keep a SetK for each group, with the keys
associated with that group. As such, I'm not sure it would be a lot
easier to implement (correctly) than FineGrainedAtomicMap.
Dan, I didn't understand why do we need to keep
On 22 Jan 2014, at 15:11, Emmanuel Bernard emman...@hibernate.org wrote:
So you don't use the AtomicMap(vs FGAM) at all? Is there any place in which
you require a lock in the whole map to be acquired?
I will be not right now.
Hum, it should read: It will be. But not right