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 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. It's just a large complicated query with a very large > result set. > > I believe part of the problem is "Perceived Performance". The SQL query > executes and returns a cursor relatively fast. I've found that > processing the result set that takes more than 90% of the response-time. > While the delegate class processes the result-set and updates the Model, > the user is made to wait. > > I've been forced to break away from a pure MVC implementation in order > to satisfy the performance needs of my client. I now employ a servlet > that opens a cursor and transforms the results in real-time. I realize > the query does not complete any faster using this method; however, users > see results in their browsers almost immediately; thus, perceived > performance is much better. > > Question: Is there a method under the MVC design pattern to accommodate > perceived performance? > > Best Regards, > Carlos Ortega > Senior Consultant > Enterprise Information Systems, Inc. > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
