Re: [collections] LRUMap wont search next "removeable" entry

[Mario Ivankovits]

Stephen Colebourne schrieb:

I'm not sure I quite follow ;-) There was a bug in the 3.0 LRUMap which
caused the wrong map entry to be passed to the protected method handling
deletion. However this is fixed in CVS.
Yes - i catched this bug and use the cvs version now.

The test case you show is the test
for the bug, and demonstrates that LRUMap can exceed its size.
 

The problem i have is:
If i add an entry to the lrumap which is locked, it blocks all other 
entries too - even if they are not blocked.

I think LRUMap.addMapping should scan until it finds an removeable entry:

The protected restriction on the LinkEntry fields is another problem fixed
in CVS - see the entryAfter() and entryBefore() methods.
 

Ah - thanks. Maybe i could implement this behaviour in my subclass.

However - i thought the LRUMap should hold all "LRU" and "Blocked" 
entries - and remove any other entry.

e.g. size = 2
add blocked A
add B
add C
the result should be
A
C
-- Mario

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]