<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>CAPI Thread Safety</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hello,<BR>
<BR>
Little introduction first. I'm working for Ingres with Andrew Ross on<BR>
the new Ingres geospatial extensions. Ingres is planning to re-use the<BR>
GEOS library through the CAPI. I've been looking over it to 1)<BR>
familiarize myself with the code and 2) to identify possible thread<BR>
safety issues.<BR>
<BR>
There are two things that jump out at me. 1) The error/notification<BR>
handlers are definitely not thread safe unless each thread can use the<BR>
same handlers. 2) The geometryFactory worries me. It seems like it may<BR>
be thread safe, such that it creates new objects only. I'm looking for<BR>
some expert opinions on that.<BR>
<BR>
I've tried to search the archives of the mailing list but the .gz files<BR>
don't seem to work for me and the online browsing isn't search-able, so<BR>
forgive me if this questions been asked before... Are there any current<BR>
plans/work being done to make the CAPI more thread safe?<BR>
<BR>
Thanks,<BR>
Chuck Thibert<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>