ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Removing methods from the Ignite cache entry API
Date Sat, 17 Jan 2015 15:14:33 GMT
I want to get some opinions about IGNITE-96:

Cache.Entry from JCache spec has a very small API and is, in fact, not much
different from Java Map.Entry. In GridGain however, the GridCacheEntry API
has many additional methods, mainly duplicating functionality from the
GridCache API.

I personally like the JCache approach and don't think we need extra methods
on the cache entry API. User can always get this functionality from the
IgniteCache API.

Can anyone think of a good reason to have additional methods on the cache
entry API?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message