On Jan 4, 2007, at 21:34, Cliff wrote:
Hi Cliff,
I'm facing FOP memory issues that I fought with a long time ago. I
lost the
battle back then and had to resort to some ugly manual page
breaking logic
and now I'm wondering the current status of the FOP project.
My immediate question is:
Do either FOP 0.20.5 or FOP Trunk address/improve on the memory issue
regarding auto page breaks?
I remember you... It was something like a second XSLT pass over the
FO input, right?
Since that time, some memory leaks have been fixed, so it could
already help you. OTOH, the issue concerning large page-sequences has
not yet been addressed, unfortunately.
Problem still remains at this point: FOP needs to build an internal
representation of the entire page-sequence before it can start any
formatting. (= due to the current architecture: the whole layout-loop
is triggered by AreaTreeHandler.endPageSequence()).
I've some ideas on how to improve the situation, but they're not
trivial adjustments, so I can't say when or even if these ideas will
make it into the codebase...
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
