[geos-devel] CAPI Thread Safety

[Martin Chapman]

Chuck,

 

You should make your own thread-safe wrapper class(es) for using GEOS in my
opinion.  That's what I do and it works great.  If you need high performance
on a server then create a thread pool manager with a semaphore around a pool
of your wrapper classes.

 

Martin

 

From: geos-devel-bounces at lists.osgeo.org
[mailto:geos-devel-bounces at lists.osgeo.org] On Behalf Of Charles Thibert
Sent: Friday, August 22, 2008 11:45 AM
To: geos-devel at lists.osgeo.org
Subject: [geos-devel] CAPI Thread Safety

 

Hello,

Little introduction first.  I'm working for Ingres with Andrew Ross on
the new Ingres geospatial extensions.  Ingres is planning to re-use the
GEOS library through the CAPI.  I've been looking over it to 1)
familiarize myself with the code and 2) to identify possible thread
safety issues.

There are two things that jump out at me.  1) The error/notification
handlers are definitely not thread safe unless each thread can use the
same handlers.  2) The geometryFactory worries me.  It seems like it may
be thread safe, such that it creates new objects only.  I'm looking for
some expert opinions on that.

I've tried to search the archives of the mailing list but the .gz files
don't seem to work for me and the online browsing isn't search-able, so
forgive me if this questions been asked before... Are there any current
plans/work being done to make the CAPI more thread safe?

Thanks,
Chuck Thibert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geos-devel/attachments/20080822/73620927/attachment.html