This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: FOP - what, where, when, how?
- From: Bertrand Delacretaz <bdelacretaz at codeconsult dot ch>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Fri, 22 Mar 2002 17:39:43 +0100
- Subject: Re: [xsl] FOP - what, where, when, how?
- Organization: codeconsult
- References: <002301c1d1b8$87e4a1e0$6b10cbc2@alastair2000> <3C9B59C7.15D68F5C@isogen.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
On Friday 22 March 2002 17:20, W. Eliot Kimber wrote:
>. . .
> If you are doing all the processing on the server you could have the
> PDF generated on demand, although this could be slow for documents
> larger than about 10 pages and would require pretty beefy servers if
> you have any significant demand on the site.
>. . .
>From my experience with FOP, it's not really the number of pages that
matter: which XSL-FO constructs you use make a huge difference.
I don't have precise rules about what constructs to avoid, but forward
references like "page N of NN" for example, can cause FOP to keep the
whole document in memory until the number of pages is known.
So I wouldn't say "larger than about 10 pages" but "depending on
document size and complexity".
--
Bertrand Delacrétaz (codeconsult.ch, jfor.org)
buzzwords: XML, java, XSLT, cocoon, mentoring/teaching/coding.
disclaimer: eternity is very long. mostly towards the end. get ready.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list