Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-q.b-one.net (mx-q.one.com [91.198.169.248])
	by mail9.b-one.net (Postfix) with ESMTP id 123F840024F
	for <info@awaresystems.be>; Fri, 18 Jun 2010 04:09:14 +0200 (CEST)
Received: by mx-q.b-one.net (Postfix, from userid 106)
	id 07BB53F36685; Fri, 18 Jun 2010 04:09:14 +0200 (CEST)
X-Virus-Scanned: by one.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-q.b-one.net (Postfix) with ESMTP id 3A1A23F29CDB for
 <info@awaresystems.be>; Fri, 18 Jun 2010 04:09:13 +0200 (CEST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id 9780E1D18E13D; Thu, 17 Jun 2010
 21:08:09 -0500 (EST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com
 [66.111.4.25]) by lists.maptools.org (Postfix) with ESMTPS id C2A141CFEFB00
 for <tiff@lists.maptools.org>; Thu, 17 Jun 2010 20:45:53 -0500 (EST)
Received: from compute1.internal (compute1.internal [10.202.2.41]) by
 gateway1.messagingengine.com (Postfix) with ESMTP id DC013FADF8; Thu, 17 Jun
 2010 21:45:52 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by
 compute1.internal (MEProxy); Thu, 17 Jun 2010 21:45:52 -0400
X-Sasl-enc: ln604IlmTamBoZ73hz/57RX3gK0FyravG1pmx6DdlrUa 1276825551
Received: from [192.168.1.125] (c-71-236-65-235.hsd1.pa.comcast.net
 [71.236.65.235]) by mail.messagingengine.com (Postfix) with ESMTPSA id
 A00C54DF042; Thu, 17 Jun 2010 21:45:51 -0400 (EDT)
Message-ID: <4C1ACFCC.80004@spicenitz.org>
Date: Thu, 17 Jun 2010 21:45:48 -0400
From: Adam Goode <adam@spicenitz.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9)
 Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4
MIME-Version: 1.0
To: Olivier Paquet <olivier.paquet@gmail.com>
References: <4C1A41A5.4070409@spicenitz.org>
 <alpine.GSO.2.01.1006171125140.12887@freddy.simplesystems.org>
 <4C1A4E8A.1060904@spicenitz.org>
 <alpine.GSO.2.01.1006171150230.12887@freddy.simplesystems.org>
 <4C1A5840.5000300@spicenitz.org>
 <AANLkTing-04iFpEr0k9-6DaA7DQFTRrFjOjdQ5g2RXM0@mail.gmail.com>
 <4C1A64CF.2060607@spicenitz.org>
 <alpine.GSO.2.01.1006171326540.12887@freddy.simplesystems.org>
 <AANLkTinwgIWMJfv8zKcO68ZHMQGK5sgyM3Pkwuw1K2_O@mail.gmail.com>
 <4C1ABEEF.7030701@spicenitz.org>
In-Reply-To: <4C1ABEEF.7030701@spicenitz.org>
X-Enigmail-Version: 1.0.1
Cc: Tiff List <tiff@lists.maptools.org>
Subject: Re: [Tiff] libtiff 4 API/ABI stability?
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1054192023=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1054192023==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigB83FD626F4B798B285EA629B"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB83FD626F4B798B285EA629B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 06/17/2010 08:33 PM, Adam Goode wrote:
> You don't need TSD to scale. Just have mostly immutable structures that=

> you lock when you write to or pass to a different thread. Then
> everything can work fine.
>=20

Actually, to clarify a little: I mean here that libtiff shouldn't
concern itself with threads, but allow the user to pass in everything
needed and treat those structures as immutable. Then a user can pass
this structure around to different threads (using proper locking and
barriers) without worrying that it will change. This is more in the
realm of thread safety #2 as I listed before.


Adam


--------------enigB83FD626F4B798B285EA629B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkwaz84ACgkQlenB4PQRJayM9ACfbYRJdvL9yE1Yza2e3N6Bj9pH
X3EAoI/9W6viPuzMrDscu6UYm12O5+0g
=JUjq
-----END PGP SIGNATURE-----

--------------enigB83FD626F4B798B285EA629B--

--===============1054192023==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
--===============1054192023==--
