I would suggest that converting spool files is not a significant process task compared to transforming HTML so I would expect it to be faster.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Saturday, 15 May 2010 4:28 a.m.
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] PDF Performance

Regarding performance, I was able to drop the time from 2 minutes, to 20 seconds, to transform a 150 page HTML document to PDF. I can live with that. Just discovering various Java optimization techniques.

That's still quite a bit less throughput than Jim Horn's example of converting a 640 page spool file in 10 seconds, using CoolSpool. But an HTML to PDF transformation offers a way to do GUI formatting, which has some added value.

I was also pleased that PDF files end up being only 1/4 - 1/5 the size of original HTML files, which may alleviate bandwidth concerns.


----- Original Message ----
From: Peter Connell <Peter.Connell@xxxxxxxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Wed, May 12, 2010 3:40:02 PM
Subject: Re: [WEB400] PDF Performance

I've been in your position before, which was to decide which of the plethora of suggestions to adopt for generating PDF from an existing web page.
My decision to use PD4ML was based on the fact that it appeared to perform very well (certainly better than BIRT), there was very little code to write in order to integrate into the existing app, there was almost no learning curve for other developers and the installation was exceedingly trivial.
Basically, I did not want my project to be hampered by any complications (including security) arising from the requirement for a PDF.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.