-
2004.11.04 19:04 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
-
2004.11.04 19:09 "Re: [Tiff] is libtiff thread-safe?", by Chris Losinger
-
2004.11.04 19:19 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
-
2004.11.04 21:10 "Re: [Tiff] is libtiff thread-safe?", by Joris Van Damme
-
2004.11.04 21:20 "Re: [Tiff] is libtiff thread-safe?", by Chris Losinger
-
2004.11.04 21:35 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
-
2004.11.04 23:09 "Re: [Tiff] is libtiff thread-safe?", by Chris Cox
- 2004.11.04 23:51 "Re: [Tiff] is libtiff thread-safe?", by Joris Van Damme
-
2004.11.04 23:09 "Re: [Tiff] is libtiff thread-safe?", by Chris Cox
-
2004.11.04 21:35 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
-
2004.11.04 21:20 "Re: [Tiff] is libtiff thread-safe?", by Chris Losinger
-
2004.11.04 21:10 "Re: [Tiff] is libtiff thread-safe?", by Joris Van Damme
-
2004.11.04 19:19 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
-
2004.11.04 19:09 "Re: [Tiff] is libtiff thread-safe?", by Chris Losinger
2004.11.04 21:35 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
Thanks for the information.
My particular situation requires the ability to handle multiple threads, each having their own TIFF*, all possibly using the RGBA interfaces for reading. And, from your deescription, it sounds like everything should be OK, *if* the RGBA stuff is able to handle multiple threads, each with their own TIFF*.
Right, *except* for the warning/error callback interfaces which we already know have problems since they do not include a pointer to user context. However, thread-specific data techniques can be used (by the application) to work-around these particular problems.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen