Hi,
No other reactions? In particular w.r.t. the open question whether it is
worth to offer a "force" mode in the situations where a dataset cannot
be re-opened (or for a band whose belonging to a dataset cannot be
determined) where the thread-safe wrapper would just put a mutex around
the calls to that dataset/band (so obviously this wouldn't scale with
the number of threads). I'm probably leaning on not offering this option
for now, if there's no obvious need it is useful. It can always been
added afterwards.
Even
Le 29/08/2024 à 14:26, Even Rouault via gdal-dev a écrit :
Hi,
I've worked on a new RFC 101: Raster dataset read-only thread-safety:
https://github.com/OSGeo/gdal/pull/10676
Summary: This RFC enables users to get instances of GDALDataset (and
their related objects such as GDALRasterBand) that are thread-safe for
read-only raster operations, that is such instances can be safely used
from multiple threads without locking.
It is backed by a preliminary implementation (fairly complete, apart
from writing new tests...). There's at least one open question raised
in the RFC.
PS: you can see one of the benefits of the migration of the doc to
ReadTheDocs hosting, with the preview of the updated documentation in
pull requests. So this is a way to mention that the move to RtD
hosting has now been completed, with the default version ("latest")
reflecting the state of the master branch, as well as the version for
the release/3.9 branch. Thanks to Dan Baston (and other people
involved) for this work! There might be a few adjustments needed, so
if you notice something unusual w.r.t. to the previous state, please
file a ticket.
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
