Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx016.isp.belgacom.be (inmx016.isp.belgacom.be [195.238.2.219])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id j2GM4jqs024883
        for <joris.at.lebbeke@skynet.be>; Wed, 16 Mar 2005 23:04:45 +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 inmx016.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j2GM4abi008963
        for <joris.at.lebbeke@skynet.be>; Wed, 16 Mar 2005 23:04:38 +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 16AF515D8F9E; Wed, 16 Mar 2005 17:04:25 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from sccimhc92.asp.att.net (sccimhc92.asp.att.net [63.240.76.166])
	by xserve.flids.com (Postfix) with ESMTP id C279515D8F7A
	for <tiff@remotesensing.org>; Wed, 16 Mar 2005 17:04:22 -0500 (EST)
Received: from quillnet (12-203-111-247.client.insightbb.com[12.203.111.247])
	by sccimhc92.asp.att.net (sccimhc92) with SMTP
	id <20050316220421i9200821ate>; Wed, 16 Mar 2005 22:04:22 +0000
Message-ID: <000601c52a74$23525b60$6502a8c0@insightbb.com>
From: "Roger Watkins" <RogerQuillDisc@insightbb.com>
To: "Joris" <joris.at.lebbeke@skynet.be>,
        "libTIFF group" <tiff@remotesensing.org>
References: <001c01c52988$4f65f460$6502a8c0@insightbb.com><001101c5298a$34494590$6aacf551@dfgrrxsknr4e>
	<000a01c52a53$18de4840$6502a8c0@insightbb.com>
	<001201c52a5f$cbd15300$4baff551@dfgrrxsknr4e>
Subject: Re: [Tiff] Need to write CCITT T.6 encoded TIFF file data
	directlytomemory buffer
Date: Wed, 16 Mar 2005 16:04:33 -0600
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: 
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: 6ed18299cb1264213f7dd044a88b8965

Joris,

Let's see if I understand this...  The application interface simply calls
the top-level functions, which are configured by TIFFClientOpen() to use the
proper I/O interface routines for the type of computer and I/O (stream,
file, buffer) called for.  Once thus configured, and with the platform
independent autoconfiguration of the CODECs that occurs during opening of
the TIFF itself, TIFFReadEncodedStrip() and TIFFWriteEncodedStrip() know
where and how to process the data provided.  As a result, to do my TStream
interface, I need only write TIFFStreamReadProc(), TIFFStreamWriteProc(),
TIFFStreamSeekProc(), TIFFStreamCloseProc(), TIFFStreamSizeProc(),
TIFFNoMapProc(), and TIFFNoUnmapProc() and a TIFFOpenStream() that calls
TIFFClientOpen() and passes it these function addresses.

One remaining question, to which I know the answer is yes, but I need to
know where to look for information:  Where do I find specifications or
requirements for writing these routines for which pointers are passed in
TIFFClientOpen()?

Thanks!  You have greatly enlightened me as to the structure and inner
workings of libTIFF!!

Roger Watkins

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