I think the scenario is slightly different in that the HTML pages actually
go through a rendering process (i.e. the HTML is parsed and such) and then
put into a PDF. I don't know how much that adds to the process.
In the end I think what Nathan is going for is the ease of creating a nice
looking web page that can subsequently double as a report without any
additional work other than running the generated HTML through a conversion
process. For those of us that have tried to create nice looking PDF reports
from scratch using things like iText, you can really appreciate how easy
tools like HTML2PDF4i make it.
On Wed, May 12, 2010 at 8:29 AM, <JDHorn@xxxxxxxxxxxxxx> wrote:
Anybody try Coolspools? Can't speak to the performance issue with numbers,
but it seems much faster than the numbers here. We have a sales management
system that creates 60,000 small pdf's every sunday. we've been using it
for years. I just did a test. It converted a 130 page spool file to a pdf
in 4 seconds (on a 520), a 640 page spool file in 10 seconds.
This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.