AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
April 2006

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2006.04.04 16:50 "BigTIFF Suggestion", by Larry Michaels
2006.04.04 21:33 "Re: BigTIFF Suggestion", by Chris Cox
2006.04.04 21:56 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.05 01:59 "Re: BigTIFF Suggestion", by Bob Friesenhahn
2006.04.05 02:22 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.06 09:46 "Re: BigTIFF Suggestion", by Gerben Vos
2006.04.06 15:11 "Re: BigTIFF Suggestion", by Bob Friesenhahn
2006.04.14 17:44 "Re: BigTIFF Suggestion", by <melser.anton@gmail.com>
2006.04.14 18:13 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.15 10:18 "Re: BigTIFF Suggestion", by <melser.anton@gmail.com>
2006.04.04 22:09 "Re: BigTIFF Suggestion", by Frank Warmerdam
2006.04.04 22:14 "Re: BigTIFF Suggestion", by Larry Michaels
2006.04.04 22:24 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.04 22:34 "Re: BigTIFF Suggestion", by Larry Michaels
2006.04.04 22:42 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.04 23:07 "Re: BigTIFF Suggestion", by Larry Michaels
2006.04.05 00:17 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.05 02:25 "Re: BigTIFF Suggestion", by Joris Van Damme
2006.04.05 11:12 "Re: BigTIFF Suggestion", by Leonard Rosenthol
2006.04.05 16:13 "Re: BigTIFF Suggestion", by Bill Bither

2006.04.04 21:56 "Re: BigTIFF Suggestion", by Joris Van Damme

Chris,

Chris Cox wrote:
> How often do applications append something to a TIFF file instead of
> writing the whole file at once?
>
> I don't think this is a common enough occurrence to change the file
> format.

I would agree...

Plus, I think TIFF is about simplicity, avoiding redundancy. Other file
formats are best at performing all kinds of tricks to optimize all kinds
of operations, and letting redundancy and complication and scruff creep
in. There are clearly benefits to that, performance-wise and
feature-wise. But TIFF is about the simplest possible form of things.
The single linked list at the very top of file format organisation is
the perfect example. There are clearly benefits to this, too.

There are little benefits to muddying the water and end up with neither
fish, nor flesh. I think it best to stick with simplicity in TIFF and
avoid as much as possible all redundancy.

Add to this that BigTIFF is designed as minimum possible change to TIFF.
One very practical reason for that, is smooth transition of existing
libraries. Larry's proposal would be a step away from that
minumum-change strategy that we've applied very consistently sofar.

And what about the fact that the BigTIFF proposal has been on-line in a
very visible place for two years now? I know of at least one complete
implementation (my own), but I think it likely some people have at least
taken some steps now, even if it's been only a proposal all this time.

I must admit Larry's proposal does have some appeal. But at the end of
the day, I'd vote against it, because of all above reasons.

If applications continuously re-open a BigTIFF file, to append some
pages... Possibly, depending on the nature of the application, they can
do some independent caching of last page offset together with file
properties like filename, file size, and file dates and such. If all
other properties are unchanged, they could assume last page offset is
unchanged, too. Perhaps that solves Larry's need without spoiling
BigTIFF, in some situations at least.


Best regards,

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