Return-Path: <tiff-bounces@remotesensing.org>
Received: from inav001.isp.belgacom.be (inav001.isp.belgacom.be [195.238.3.91])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iA59K9Yi024325
        for <joris.at.lebbeke@skynet.be>; Fri, 5 Nov 2004 10:20:09 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inas006.isp.belgacom.be (localhost [127.0.0.1])
        by inav001.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id iA59K2O9001883
        for <joris.at.lebbeke@skynet.be>; Fri, 5 Nov 2004 10:20:03 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inmx015.isp.belgacom.be (inmx015.isp.belgacom.be [195.238.2.218])
        by inas006.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id iA59JosN020008
        for <joris.at.lebbeke@skynet.be>; Fri, 5 Nov 2004 10:20:00 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx015.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iA59JdNC021126
        for <joris.at.lebbeke@skynet.be>; Fri, 5 Nov 2004 10:19:40 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 35916449ECC; Fri,  5 Nov 2004 04:19:25 -0500 (EST)
X-Original-To: Tiff@remotesensing.org
Delivered-To: Tiff@remotesensing.org
Received: from outmx001.isp.belgacom.be (outmx001.isp.belgacom.be
	[195.238.3.51])
	by xserve.flids.com (Postfix) with ESMTP id 369E3449EA8
	for <Tiff@remotesensing.org>; Fri,  5 Nov 2004 04:19:23 -0500 (EST)
Received: from outmx001.isp.belgacom.be (localhost [127.0.0.1])
	by outmx001.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id iA59JKQp027486
	for <Tiff@remotesensing.org>; Fri, 5 Nov 2004 10:19:20 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (93-217.241.81.adsl.skynet.be [81.241.217.93])
	by outmx001.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id iA59JHBU027462; Fri, 5 Nov 2004 10:19:17 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <002501c4c318$8b95fab0$5dd9f151@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>
References: <LOENLAKPHCMDKNAAGBHCAEEECAAA.jxu@cvisiontech.com><Pine.SOC.4.60.0411041303330.9670@blade.simplesystems.org><6.0.0.22.1.20041104140811.02611f48@pop.earthlink.net><Pine.SOC.4.60.0411041311570.9670@blade.simplesystems.org><001101c4c2b2$c5616c40$a304f151@dfgrrxsknr4e><6.0.0.22.1.20041104161558.025fb5a0@pop.earthlink.net><Pine.SOC.4.60.0411041531590.9670@blade.simplesystems.org><p05210608bdb066d92f01@[153.32.48.223]><000f01c4c2c9$2a9f1420$3825c850@dfgrrxsknr4e>
	<Pine.SOC.4.60.0411041834110.9670@blade.simplesystems.org>
Subject: Re: [Tiff] is libtiff thread-safe?
Date: Fri, 5 Nov 2004 10:19:24 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Cc: Tiff@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 5975359a9ee950b87694fe33b829e586

> > I totally fail to see the connection between the lack of TIFF * parameter in
the
> > callbacks on the one hand, and multi-threading on the other. The callbacks
are
>
> In that case I will attempt to educate you.

How fortunate.

> If the functions provided a pointer to user context
> then the error information could simply be stored there, without any
> need to use an OS-specific thread-API function to support
> thread-specific storage.

My point exactly. In other words, if the function were adequate... there would
be not threading issue, nor any other issue of tracing back the error to its
context, nor any other issue of storing the error description in the right
place. In my view, that means the issue is not threading specific, not threading
related.

Investigating the above quote the other way around now, the functions *not*
providing a pointer to user context, the thread specific storage (threadvars or
whatever) are *not* going to help you if the thread uses multiple TIFF *. It's
still not possible in that case to trace back to user context.

In other words, threading is not related to this issue.


Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
