| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Steven Schlansker <stevenschlansker(at)gmail(dot)com> |
| Cc: | Markus KARG <markus(at)headcrashing(dot)eu>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Adding new dependencies for in-core |
| Date: | 2015-06-30 18:31:02 |
| Message-ID: | CAB=Je-FuDzg0An3C6MqgyO8dYWe3rw_gT_LC1yd4k_GrasuOyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> it is not hard to replace it internally even if it breaks the not-public-API
I fully agree here. Sorry that we moved off-topic.
>Final note, is a ConcurrentLinkedHashMap actually the data structure we should be using?
I am not yet sure which API of CLHM would be used. I just assume CLHM
allows some "smart eviction".
If it turns out CLHM is a no-no in pgjdbc, I might have to resort to a
org.postgresql.util.LruCache[128] kind of data structure.
I do not like that very much (even though it would make me a bit happy
for reusing my own code), so I want feedback on policy of using
dependencies.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus KARG | 2015-06-30 20:04:50 | Re: SQLJSON |
| Previous Message | Steven Schlansker | 2015-06-30 18:22:12 | Re: Adding new dependencies for in-core |