thread safety and OGR

[Tamas Szekeres]

Frank,

I'm +0 on this issue since it is a symptomatic treatment but we should
also discover the particular reason of the issue. We should also
aspire to support the independent execution of the multiple threads as
much as we can.
As far as I remember the GetFieldAsString problem of OGR have been
treated as of RFC-6 as a "side effect".

We might want to ask the client for testing with the latest OGR. It
would be also practical to see whether your temporary fix really
solves the client's problem or not. If yes I would be interested in
tracking down the root of the problem at the OGR level.

Best regards,

Tamas Szekeres



2007/8/20, Frank Warmerdam <warmerdam at pobox.com>:
> Folks,
>
> I have a client who would like to see OGR thread safety in MapServer
> implemented.  The issue is recorded in Trac as:
>
>    http://trac.osgeo.org/mapserver/ticket/1977
>
> However, we are quite late in our release cycle and I can see some
> ambiguity about whether this is really a bug fix, or really a new feature
> in bug-fix-clothing.  So, I have a patch ready to make mapogr.cpp thread
> safe using the normal Mapserver thread lock facilities.  How do we feel
> about my applying it?
>
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGeo, http://osgeo.org
>