[infinispan-dev] Design session today
Manik Surtani
msurtani at redhat.com
Fri Aug 9 07:39:06 EDT 2013
On 9 Aug 2013, at 12:06, Sanne Grinovero <sanne at infinispan.org> wrote:
>>> 3. allowing the cache loader to expose unserialised data directly (ValueHolder.getBytes[]).
>>
>> I used the name ValueHolder but this is a really poor term - how about ContentsProxy? It is a proxy for the contents of the entry, exposing methods:
>>
>> interface ContentsProxy {
>> ByteBuffer getValueBuffer();
>> ByteBuffer getInternalCacheValueBuffer();
>> InternalCacheValue getInternalCacheValue();
>>
>> // Same as above except this method only deserializes timestamps and metadata. Not the actual value.
>> InternalCacheValue getSparseInternalCacheValue();
>> }
>
> +1 for the name "ContentsProxy".
> On exposing ByteBuffer .. I'm wondering if we shouldn't have our own
> interface, potentially shared with JGroups. For example, I'd like to
> see an appendToEnd capability and an insertToHead which don't require
> to eagerly resize the underlying arrays.
https://docs.jboss.org/infinispan/5.2/apidocs/index.html?org/infinispan/io/ByteBuffer.html
--
Manik Surtani
More information about the infinispan-dev
mailing list