Changes between Version 3 and Version 4 of rfc16_ogr_reentrancy


Ignore:
Timestamp:
Sep 4, 2007, 9:02:45 AM (17 years ago)
Author:
warmerdam
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rfc16_ogr_reentrancy

    v3 v4  
    3131
    3232Note that layers cannot be threadsafe as long as layer feature reading status is implicit in the layer object.  The default return value for all test values is FALSE, as is normal for the !TestCapability() method, but specific drivers can return TRUE after determining that the driver datasources or layers are in fact reentrant and/or threadsafe.
     33
     34== OGRSFDriverRegistrar ==
     35
     36Various changes have already been made to make the driver registrar thread safe, primarily by protecting operations on it with a mutex.
     37
     38== OGRSFDriver ==
     39
     40No changes are required to the OGRSFDriver base class for thread safety, primarily because it does almost nothing.
     41
     42== OGRDataSource ==
     43
     44This class has been modified to include an m_hMutex class data member which is a mutex used to ensure thread safe access to internal datastructures such as the layer list.  Classes derived from OGRDataSource that wish to implement threadsafe operation should use this mutex when exclusivity is required.
     45
     46