2010.06.17 15:39 "[Tiff] libtiff 4 API/ABI stability?", by Adam Goode

2010.06.18 02:36 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn

On Thu, 17 Jun 2010, Olivier Paquet wrote:

That's fine for most operations but at some point (eg. file I/O if it is not memory mapped) we will need synchronization. Which pretty much means linking with pthread. This is why I raised the question: should we do it now or wait until is is actually needed?

It is certainly true that in some OS environments, the library might not operate in in a thread-safe manner unless it is explicitly built as thread safe code. For example global 'errno' needs to be handled specially in a threaded program. It is also true that multiple threads will not be able to use the same file descriptor without doing locking. For many/most people, they will be happy if libtiff works flawlessly while doing I/O to several TIFF files from several threads simultaneously with a thread per file model.

Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/