Thread:

From
Vladimir Sitnikov
Date:
There should be some implementation behind that "strategy" anyway.

BTW. CLHM implements java.util.concurrent.ConcurrentMap, so I think it
is a safe interface for replacement in the future (e.g. to
https://github.com/ben-manes/caffeine when we have jdk8-minimum
builds)

Vladimir


Re:

From
"Markus KARG"
Date:
Yes, sure, but having a strategy in-between at least adds room to do LRU by hand in case we don't want to shade more
andmore third party dependencies thanks to pgjdbc's apparent no-dependency policy. 

-----Original Message-----
From: Vladimir Sitnikov [mailto:sitnikov.vladimir@gmail.com]
Sent: Dienstag, 30. Juni 2015 20:05
To: Markus KARG
Cc: List
Subject:

There should be some implementation behind that "strategy" anyway.

BTW. CLHM implements java.util.concurrent.ConcurrentMap, so I think it
is a safe interface for replacement in the future (e.g. to
https://github.com/ben-manes/caffeine when we have jdk8-minimum
builds)

Vladimir



Re:

From
"Markus KARG"
Date:
You just don't give up hope, don't you? I doubt that I will see the day when we may use JRE 8 APIs before I reach
retirementage. ;-) 


-----Original Message-----


BTW. CLHM implements java.util.concurrent.ConcurrentMap, so I think it is a safe interface for replacement in the
future(e.g. to https://github.com/ben-manes/caffeine when we have jdk8-minimum 
builds)

Vladimir


--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc