Right, I had been thinking along those lines as well, but am not familiar
enough with the code to be able to tell if this is worth pursuing. At first
I thought it would be pretty memory-intensive to keep all those images in
memory, but then I realized that is what you do anyway, since you first
create the DOM tree. (In my version everything was written to output
immediately:) In fact, being able to tell if you already have the image data
will even reduce memory usage.
Paul
-----Original Message-----
From: Thomas E Deweese [mailto:[EMAIL PROTECTED]]
Vincent makes some good points about the general case, however I
will add one additional comment which is that computing a checksum on
the encoded data should be significantly cheaper than the encoding
processes it's self (so you could encode the data, check if the
checksum matches (BTW the PNG encoder has a CRC generator) a
pre-existing image, check the encoded data byte by byte, just to be
sure, if everything checks out just use a reference).
This is a quite a bit more work (and quite a bit slower) but would
be usable for the general case. For now just having a simple minded
version (that might eventually grow into a general solution with
options) would be great though.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
