incubator-directmemory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <simonetrip...@apache.org>
Subject Re: [jira] [Commented] (DIRECTMEMORY-43) Cache should allow key objects instead of plain string
Date Sat, 18 Feb 2012 20:20:53 GMT
IIUC, shouldn't the allocate(key, size) method be an "internal-only"
method? I mean, it should be used only when a non-null object has to
be stored... or not?
sorry for the silly question!

TIA,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Sat, Feb 18, 2012 at 9:14 PM, Simone Tripodi
<simonetripodi@apache.org> wrote:
> +1 to Mau, there is no fault here, Raf!!!
>
> just to remark that we have been doing a community work here, joining
> efforts to make a better product than everybody could make
> individually! :)
>
> What I didn't understand, while applying generics, is why at at a
> certain point, Pointer.clazz becomes ByteBuffer.class, when it could
> safety be the type of stored object...
>
> Any hint?
> TIA,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Sat, Feb 18, 2012 at 6:35 PM, Raffaele P. Guidi
> <raffaele.p.guidi@gmail.com> wrote:
>> What about NIOTest in org.apache.directmemory.memory?
>>
>> On Sat, Feb 18, 2012 at 6:20 PM, Maurizio Cucchiara
>> <mcucchiara@apache.org>wrote:
>>
>>> Ciao Raffaele,
>>> there is no fault, we are still in time to write a small test :) (and maybe
>>> it would be better if you write it, since you are the one with the deeper
>>> overall view).
>>>
>>> Twitter     :http://www.twitter.com/m_cucchiara
>>> G+          :https://plus.google.com/107903711540963855921
>>> Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
>>>
>>> Maurizio Cucchiara
>>>
>>>
>>> On 18 February 2012 18:09, Raffaele P. Guidi <raffaele.p.guidi@gmail.com
>>> >wrote:
>>>
>>> > Uhm I guess this is my fault...
>>>

Mime
View raw message