[postgis-devel] Common Code

[Bryce L Nordgren]

On Tue, Aug 9, 2011 at 9:36 AM, Mark Cave-Ayland <
mark.cave-ayland at siriusit.co.uk> wrote:

> Not so much the caching (as the PROJ.4 API is similar in this aspect), but
> the ability to detect memory leaks within the caching code and a fixed API
> for caching in general. Then we can write a set of function callbacks to
> make adding caching to any other function within PostgreSQL really easy.
>
>
The thing that gives me pause is making a generic caching facility in a
language like C. Polymorphism is really hard in that environment, as
indicated by the lack of generic caching libraries in C. The hard part is
not necessarily just storing the pointer to an opaque type, but  figuring
out whether you have a cache hit or not. Sounds like a pandora's box to me.

What about using BerkeleyDB in a RAM only configuration as a key/value
store? It's mature, stable, and multiplatform.

Bryce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20110809/39862b6d/attachment.html>