Re: libmng data-push mechanism(s)

> Well, if you put in a good API you can always optimize later...

See my answer to Alex. (not that I'm claiming it's good tho!! ;)
 
> I don't know that it's so important; either way you have the memory
> footprint. A submit/release scheme covers our requirements, and I don't
> think it's much extra work for someone who just wants to push and
> forget.

True enough.
 
> Of course, if you *really* care about memory footprint, you need to be
> able to seek to recover past chunks you need that you don't have room to
> store. :)

But that would also mean re-decoding the IDAT's and JDAT's which will give 
more cpu overhead. It would be useful in memory-deprived systems tho, but 
that's for another time...
 
> Thanks for being so responsive though; it's really helping our project.

You're welcome!

Gerard

Gerard Juyn
[email protected]
www.datapartners.nl

--
Send the message body "help" to [email protected]