Rendering can be slow. Sometimes one can render on the client (Ex: Stxx,
XFroms, XUL, JavaScript, ActionScript) .
(My experience hs been optimizing data retrieve as slow part) I use
iReports, not sure what you are using to render, maybe just a faster
XSLT is needed. (and if data or styles are
I have a client that requires very large reports to be rendered
dynamically in various formats, HTML, PDF, XML, etc. Various clients
have complained about system performance. The database has already been
optimized and the delegate class responsible for managing the dataset is
very efficient.
To maintain a separation of your data layer and presentation you could
wrap an Iterator implementation around your ResultSet. That allows you to
change the persistence mechanism without any other code changing.
David
--- Ortega, Carlos [EMAIL PROTECTED] wrote:
I have a client that requires
Off hand, I'm not sure if you've broken from a pure MVC implementation.
If you are using server pages, it's a good idea to keep the model code
out of the server page, since you end up mixing concerns within the same
component.
But if your servlet is designed so that, internally, the model code
4 matches
Mail list logo
