thread safety and OGR

[Sean Gillies]

Or how about making OGR thread safe(r)? That's the root issue, yes?

Sean

Howard Butler wrote:
> I'm +1 on including it, assuming the release manager lets it in.  We  
> already have precedence for a number of quasi bug/features related to  
> AGG this release, and the behavior of MapServer's locking facilities  
> in other contexts is well known.
> 
> /me calls unprotected OGR a bug.
> 
> Howard
> 
> On Aug 19, 2007, at 5:25 PM, Frank Warmerdam wrote:
> 
>> 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
>