Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-s.b-one.net (mx-s.one.com [91.198.169.250])
	by mail9.b-one.net (Postfix) with ESMTP id DB4D4400614
	for <info@awaresystems.be>; Tue, 30 Nov 2010 21:00:34 +0100 (CET)
Received: by mx-s.b-one.net (Postfix, from userid 106)
	id C74061BF29C1; Tue, 30 Nov 2010 20:59:58 +0100 (CET)
X-Virus-Scanned: by one.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=0 required=4
 tests=[HTML_MESSAGE=0.001]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-s.b-one.net (Postfix) with ESMTP id B4CDC102AC2 for
 <info@awaresystems.be>; Tue, 30 Nov 2010 20:59:57 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id 6B2D61D1B0007; Tue, 30 Nov 2010
 14:59:18 -0500 (EST)
Received: from mk-filter-1-a-1.mail.uk.tiscali.com
 (mk-filter-1-a-1.mail.uk.tiscali.com [212.74.100.52]) by lists.maptools.org
 (Postfix) with ESMTP id 62FB01D1B0005 for <tiff@lists.maptools.org>; Tue, 30
 Nov 2010 14:58:18 -0500 (EST)
X-Trace:
 541606362/mk-filter-1.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/88.110.247.139/None/johne53@tiscali.co.uk
X-SBRS: None
X-RemoteIP: 88.110.247.139
X-IP-MAIL-FROM: johne53@tiscali.co.uk
X-SMTP-AUTH: 
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Apple Mail (2.1078)
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8GAOvk9ExYbveL/2dsb2JhbACCA5MIjgtyxC+CE4M0BI1l
X-IronPort-AV: E=Sophos;i="4.59,281,1288569600"; 
 d="scan'208,217";a="541606362"
Received: from 88-110-247-139.dynamic.dsl.as9105.com (HELO mac-mini.lan)
 ([88.110.247.139]) by smtp.tiscali.co.uk with ESMTP; 30 Nov 2010 19:58:16
 +0000
From: John Emmas <johne53@tiscali.co.uk>
Mime-Version: 1.0 (Apple Message framework v1078)
Date: Tue, 30 Nov 2010 19:58:08 +0000
In-Reply-To: <4CF55000.7000109@telegraphics.com.au>
To: tiff@lists.maptools.org
References: <76394064-A6C2-46E1-BC59-DB187EDDD275@tiscali.co.uk>
 <4CF55000.7000109@telegraphics.com.au>
Message-Id: <313060CD-61A2-4853-A24D-EFD393C830DE@tiscali.co.uk>
X-Mailer: Apple Mail (2.1078)
Subject: Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up
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="===============1943616216=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org


--===============1943616216==
Content-Type: multipart/alternative; boundary=Apple-Mail-1--692723670


--Apple-Mail-1--692723670
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 30 Nov 2010, at 19:26, Toby Thain wrote:

>=20
> Can't the existing tif_unix entry points be used, if the application
> wants to use POSIX file handles?
>=20
I didn't have time to try that today but I figure it would probably work =
fine.  It's not as intuitive though as using tif_win32.  You'd have to =
know up front that the unix entry points apply if you wish to use =
libTIFF in conjunction with a POSIX based, 3rd party library.  Most devs =
probably wouldn't assume that and would most likely just use the =
supplied win32 interfaces (I did).  Especially since the POSIX style =
function calls are already present in Win32?!?

Of course, I realise that this is the kind of problem one only =
appreciates with the benefit of hindsight..!  :-)


On 30 Nov 2010, at 19:24, Ian Ashley wrote:

>=20
> How about using TIFFClientOpen and providing your own callbacks for =
reading, writing, etc?
>=20
Okay, that's a good idea that didn't occur to me.  I'm tempted to look =
into it - but.....


On 30 Nov 2010, at 19:43, Kevin Myers wrote:

> I haven't looked into this very much *at all*, so what I am about to =
say=20
> could easily be *very* wrong.  That being said, wouldn't changing =
libtiff to=20
> use read() and write() break large file handling (greater than 4GB) =
under=20
> Win32?

Hmmm....  okay, that's a pretty good reason if it's true!

John=

--Apple-Mail-1--692723670
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 30 Nov 2010, at 19:26, Toby Thain =
wrote:</div><br><blockquote type=3D"cite"><div><br>Can't the existing =
tif_unix entry points be used, if the application<br>wants to use POSIX =
file handles?<br><br></div></blockquote><div>I didn't have time to try =
that today but I figure it would probably work fine. &nbsp;It's not as =
intuitive though as using tif_win32. &nbsp;You'd have to know up front =
that the unix entry points apply if you wish to use libTIFF in =
conjunction with a POSIX based, 3rd party library. &nbsp;Most devs =
probably wouldn't assume that and would most likely just use the =
supplied win32 interfaces (I did). &nbsp;Especially since the POSIX =
style function calls are already present in =
Win32?!?</div><div><br></div><div>Of course, I realise that this is the =
kind of problem one only appreciates with the benefit of hindsight..! =
&nbsp;:-)</div><div><br></div><div><br></div>On 30 Nov 2010, at 19:24, =
Ian Ashley wrote:</div><div><br></div><blockquote type=3D"cite"><div><font=
 face=3D"Calibri, Verdana, Helvetica, Arial"><span style=3D"font-size: =
11pt; "><br>How about using TIFFClientOpen and providing your own =
callbacks for reading, writing, =
etc?<br><br></span></font></div></blockquote>Okay, that's a good idea =
that didn't occur to me. &nbsp;I'm tempted to look into it - =
but.....<div><br></div><div><br></div><div><div>On 30 Nov 2010, at =
19:43, Kevin Myers wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I =
haven't looked into this very much *at all*, so what I am about to =
say&nbsp;<br>could easily be *very* wrong. &nbsp;That being said, =
wouldn't changing libtiff to&nbsp;<br>use read() and write() break large =
file handling (greater than 4GB) =
under&nbsp;<br>Win32?<br></div></blockquote><br></div><div>Hmmm.... =
&nbsp;okay, that's a pretty good reason if it's =
true!</div><div><br></div><div>John</div></body></html>=

--Apple-Mail-1--692723670--

--===============1943616216==
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/
--===============1943616216==--
