I won't say it is over-engineering: I think it is always a good idea to *explicitly* pick a strategy instead of taking
one*for granted* just because it comes with the box. For example, at the JCP we discuss the intensive use of the Java
CacheAPI for various endavious exactly like this one. :-)
-----Original Message-----
From: Vladimir Sitnikov [mailto:sitnikov.vladimir@gmail.com]
Sent: Dienstag, 30. Juni 2015 20:14
To: Steven Schlansker; Markus KARG
Cc: List
Subject: Re: [JDBC] Adding new dependencies for in-core
>I'm having trouble believing any end user will replace the caching strategy for prepared statements.
My wild guess is Markus a bit over-engineers _internal_ implementation of the driver.
I think he hints best practices of coding so the driver does not get tied to the single cache implementation.
Markus, did I get you right?
Vladimir
