Return-Path: <tiff-bounces@remotesensing.org>
Received: from inav004.isp.belgacom.be (inav004.isp.belgacom.be [195.238.3.237])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iANM5PID029489
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 23:05:25 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inas001.isp.belgacom.be (localhost [127.0.0.1])
        by inav004.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id iANM5GjE029311
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 23:05:18 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inmx013.isp.belgacom.be (inmx013.isp.belgacom.be [195.238.2.216])
        by inas001.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id iANM59iT003167
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 23:05:11 +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 inmx013.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iANM51o6022791
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 23:05:05 +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 776EB49CFB6; Tue, 23 Nov 2004 17:04:48 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from mail.sidefx.com (tor149-99-58-193.dedicated.sprintdsl.ca
	[149.99.58.193])
	by xserve.flids.com (Postfix) with ESMTP id B1A2C49CF93
	for <tiff@remotesensing.org>; Tue, 23 Nov 2004 17:04:46 -0500 (EST)
Received: from [192.168.237.144] (crete.ithaca.sidefx.com[192.168.237.144])
	by mail.sidefx.com (Smail-3.2.0.111 2000-Feb-17 #5; 2004-May-20)
	(1985 bytes) via sendmail with /P:esmtp/R:inet_hosts/T:smtp
	id <m1CWimE-004coPC@mail.sidefx.com> (sender <edward@sidefx.com>)
	for <tiff@remotesensing.org>; Tue, 23 Nov 2004 17:04:46 -0500 (EST)
Message-ID: <41A3B404.9020506@sidefx.com>
Date: Tue, 23 Nov 2004 17:04:52 -0500
From: Edward Lam <edward@sidefx.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: [Tiff] compatibility patch
References: <1100715200.10008.26.camel@rode.parc.com>
	<20041123203437.GA12262@ak4719.spb.edu>
	<Pine.SOC.4.60.0411231455110.9670@blade.simplesystems.org>
	<41A3AA8E.5090400@sidefx.com>
	<Pine.SOC.4.60.0411231545220.9670@blade.simplesystems.org>
In-Reply-To: <Pine.SOC.4.60.0411231545220.9670@blade.simplesystems.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: 2c026c5ea5058b02848fd3667b15d1f9

So somehow combining the best of both files. I think we want:
- 4GB files
- memory-mapped files
- the more user-friendly Win32 error handler from tif_win32.c

Regards,
-Edward

Bob Friesenhahn wrote:
> On Tue, 23 Nov 2004, Edward Lam wrote:
> 
>> Hi Bob,
>>
>> If you look at the MSVCRT source, they are basically just wrappers 
>> around the Win32 functions used in tif_win32.c anyhow. I would suggest 
>> that you take a look yourself at tif_win32.c. I think that tif_win32.c 
>> might also be more 64-bit friendly. If we have 4GB issues, they will 
>> likely lie more with the fact that t_sizet is defined as int32 instead 
>> of uint32.
> 
> 
> Right.  Even though NTFS can support huge files, most 32-bit Windows 
> file access APIs are limited to supporting 2GB due to use of 32-bit 
> signed offsets.  Success can be achieved by using the POSIX-style 
> underscore APIs (_read, _write, etc.).
> 
> Bob
> ======================================
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us
> http://www.simplesystems.org/users/bfriesen
> 
> 

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