Re: Java memory overload with FOP and RenderX

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey, Dan.

It's also worth noting that FOP keeps an entire page-sequence in memory 
before serializing (and I'd be surprised if RenderX did any different); 
breaking down a document into smaller page-sequences can seriously ease 
memory usage.  (In one extreme case, a massive document that was completely 
un-processable was broken down into one-page page-sequences and went 
through FOP just fine.)

There's also a fop-user list for questions specific to FOP; it's archived 
at <URL: http://marc.theaimsgroup.com/?l=fop-user&r=1&w=2 > and the 
subscription address is fop-user-subscribe@xxxxxxxxxxxxxxx

~Chris
- -- 
Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc.
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: http://www.hmmci.com/ > <URL: http://crism.maden.org/consulting/ >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQA/AwUBPGI+jqxS+CWv7FjaEQL5ygCgsUHVC/Wt1rAyRHsuBe/MUolWsE0AoIwZ
/uZ1fQCkVC0e+nNjb666Okx9
=Vaap
-----END PGP SIGNATURE-----


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list