AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
November 2004

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2004.11.04 18:31 "is libtiff thread-safe?", by James Xu
2004.11.04 19:04 "Re: is libtiff thread-safe?", by Bob Friesenhahn
2004.11.04 19:09 "Re: is libtiff thread-safe?", by Chris Losinger
2004.11.04 19:19 "Re: is libtiff thread-safe?", by Bob Friesenhahn
2004.11.04 21:10 "Re: is libtiff thread-safe?", by Joris Van Damme
2004.11.04 21:20 "Re: is libtiff thread-safe?", by Chris Losinger
2004.11.04 21:35 "Re: is libtiff thread-safe?", by Bob Friesenhahn
2004.11.04 23:09 "Re: is libtiff thread-safe?", by Chris Cox
2004.11.04 23:51 "Re: is libtiff thread-safe?", by Joris Van Damme
2004.11.05 00:40 "Re: is libtiff thread-safe?", by Bob Friesenhahn
2004.11.05 00:53 "Re: is libtiff thread-safe?", by Phillip Crews
2004.11.05 12:19 "Re: is libtiff thread-safe?", by John Aldridge
2004.11.05 12:50 "Re: is libtiff thread-safe?", by Joris Van Damme
2004.11.05 01:06 "Re: is libtiff thread-safe?", by Chris Cox
2004.11.05 09:19 "Re: is libtiff thread-safe?", by Joris Van Damme
2004.11.05 14:38 "Re: is libtiff thread-safe?", by Bob Friesenhahn

2004.11.04 23:09 "Re: is libtiff thread-safe?", by Chris Cox

At 3:35 PM -0600 11/4/04, Bob Friesenhahn wrote:
> On Thu, 4 Nov 2004, Chris Losinger wrote:
>
> > 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.

Documenting that issue and suggesting that the callbacks contain a 
mutex or critical section (if thread safety is an issue) might be a 
good idea.

Chris